Public leaderboard

Public assessment

endiagram/mcp (@endiagram/mcp)

endiagram-mcp · v0.3.16 · scanned

What changed in the harness

Selection accuracy 98→93, token cost up 1%, unconfirmed writes 0%→0%.

Category breakdown

Where the score comes from.

Earned points across the four signals Gradable measures. Safety and Legibility are scored out of 30; Economics and Discoverability are scored out of 20.

01Safety

0.0 / 30

0.0 out of 30
02Legibility

28.8 / 30

28.8 out of 30
03Economics

19.4 / 20

19.4 out of 20
04Discoverability

13.5 / 20

13.5 out of 20

Highest-impact fix

Estimated gain +30 points

Add explicit identity and permission preflight tools

Expose machine-readable principal/tenant confirmation and a non-mutating permission check so agents can verify both before destructive actions.

Description evidence

Defects and rewrites.

3 defects found across the exposed tool descriptions. Suggested rewrites make purpose, inputs, boundaries, and returns easier for an agent to understand.

Tool Defect types Suggested rewrite
live
no_return_description
Can it deadlock? Can entities overflow? Returns isStructurallyLive (true means every siphon contains a trap — no structural deadlock possible), uncoveredSiphons (entity groups that can drain permanently, with the actors and locations affected), isStructurallyBounded (true means no entity can accumulate without limit), and unboundedCycles (action sequences that could cause overflow). See the server instructions for EN language syntax.
reachable
no_return_description
Can X reach Y? Follows directed data flow first; falls back to undirected. `from` and `to` accept entity names or action names (resolved against the program). Returns whether Y is reachable from X, a path showing each step with actor and location, a locationCrossings count of boundary transitions, and — when defense_nodes is given — a coverage report (coverage.fullCoverage=false means unguarded routes exist). See the server instructions for EN language syntax.
equivalent
no_return_description
Are two systems the same, or what changes if I change this one? Compare mode (source_a + source_b) returns structural differences, edit distance, and spectral equivalence, where isCospectral=true means identical graph structure up to relabeling — topologically the same despite different names, actors, or locations. Evolve mode (source + patch) dry-runs a change and returns a diff plus any new or lost bridge nodes. Patch has three directive types — plain EN statement adds an action; a line starting with `-` (and not containing `do:`) removes the named action; a statement whose action name matches an existing one replaces the original. See the server instructions for EN language syntax.

Selection evidence

Confusable tool pairs.

0 pairs where similar names or overlapping descriptions may send an agent toward the wrong tool.

Tool A Tool B Confidence Why they collide
No confusable tool pairs were flagged in this assessment.

Compare the field

One score is useful.
The evidence makes it actionable.

Back to the leaderboard