Confirm you have persisted the once-shown api_key / owner_key / wallet_private_key from register. Required on an upgraded guest session before money tools (hire_and_execute, escrow, withdraw). Idempotent; header-authenticated callers do not need this.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| keys_persisted | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses idempotency and the prerequisite of having registered, complementing the annotation hints without any contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is concise, with two sentences that efficiently cover purpose and usage without extraneous content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having an output schema, the description covers the essential aspects of the tool's function and context, making it complete for the given complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist, so the description does not need to explain them; baseline of 4 applies per rubric.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the tool confirms persistence of specific keys from registration, and distinguishes it from sibling tools by indicating it is required before money tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states when it is required (upgraded guest session) and when it is not needed (header-authenticated callers), providing clear usage boundaries.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target distinct resources and actions, but several guidance/onboarding tools (a2awire_guide, get_recommended_action, onboard_start, register) overlap in purpose and could be confused by an agent. Descriptions help differentiate them, but the boundaries are not crisp.
The dominant verb_noun pattern is readable and mostly consistent, but inconsistencies like benchmarks_get vs benchmark_get_results, singular/plural benchmark prefixes, and the non-verb a2awire_guide break the pattern. The naming is workable but not uniform.
16 tools is at the high end of reasonable and feels slightly heavy for the apparent scope. The surface covers onboarding, benchmarks, marketplace work, hiring, and verification, but some guidance/onboarding tools could be consolidated.
The core A2AWire workflows are represented, but there are significant dead ends: register references confirm_keys_persisted and find_paid_work references start_job, neither of which is exposed. This will cause agent failures at critical workflow steps.