Public leaderboard

Public assessment

wazionapps/mcp-server (@wazion/mcp-server)

wazion-mcp-server · v1.2.0 · scanned

What changed in the harness

Selection accuracy 100%, destructive-action safety rate 0% (baseline only -- no rewrite pass applied).

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

29.7 / 30

29.7 out of 30
03Economics

20.0 / 20

20.0 out of 20
04Discoverability

20.0 / 20

20.0 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.

0 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
No description defects were flagged in this assessment.

Selection evidence

Confusable tool pairs.

1 pair where similar names or overlapping descriptions may send an agent toward the wrong tool.

Tool A Tool B Confidence Why they collide
create_account activate_account medium Both tool names center on account/PIN, and create_account explicitly handles existing accounts by requesting a login PIN, so a task phrased like 'I need to get into my account' or 'I have a code, set up my access' is ambiguous between requesting the PIN (create_account) and verifying it (activate_account). Distinguishing requires reading the descriptions carefully rather than the name alone.

Compare the field

One score is useful.
The evidence makes it actionable.

Back to the leaderboard