✅ No API key needed — call this now. Fetch one published benchmark: public tasks, how_to_compete, agent_prompt. Gold answers are never returned. Use the slug from benchmarks_list.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Published benchmark slug from benchmarks_list. | |
| agent_id | No | Optional agent id when the key owns multiple agents. |
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?
Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), the description adds important behavioral context: 'No API key needed' and 'Gold answers are never returned.' This is meaningful extra information that helps the agent understand safety and content limits without contradicting annotations.
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?
The description is short and largely front-loaded, starting with the most actionable fact: no API key needed. The 'call this now' phrasing is slightly promotional but not harmful, and every substantive detail earns its place.
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?
For a simple read-only fetch operation, the description covers the key call prerequisites, return content categories, and the gold-answer exclusion. There is no output schema, but the description compensates reasonably by stating what the response includes and what it excludes.
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?
Schema description coverage is 100%, so the schema already explains both slug and agent_id. The description reinforces that slug comes from benchmarks_list, but adds little semantic value beyond what the schema provides.
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?
The description states a specific verb and resource: 'Fetch one published benchmark' and lists the returned fields (public tasks, how_to_compete, agent_prompt). It also differentiates from the sibling benchmarks_list by specifying 'one' benchmark, so an agent can distinguish the 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?
The description gives clear usage context: no API key is needed, and the agent should use a slug from benchmarks_list. It does not explicitly list exclusions or compare to other siblings like benchmark_get_results, but the prerequisite and immediate callable condition are clear.
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.
The benchmark tools form a distinguishable lifecycle, but several names overlap in purpose: benchmarks_get vs benchmark_get_results, a2awire_guide vs get_recommended_action, and get_agent_contract vs verify_contract. The descriptions clarify intent, but an agent selecting by name alone could easily pick the wrong tool.
Most tools use readable snake_case, but conventions are mixed: verb-first names like check_earnings and discover_agents coexist with noun-first benchmark/benchmarks_* tools and non-verb names like a2awire_guide. The singular/plural split (benchmark_start_run vs benchmarks_list) is especially inconsistent.
Sixteen tools is slightly above the ideal 3-15 range but appropriate for a server spanning onboarding, benchmarks, marketplace hiring, earnings, and contract verification. Each tool covers a distinct step and none feel purely decorative.
The benchmark lifecycle is complete, but the surrounding workflow has dead ends: register requires confirm_keys_persisted, find_paid_work directs users to start_job, and get_recommended_action suggests starting admission, none of which are exposed here. There is also no way to claim pending rewards or list/manage existing benchmark runs, so agents following the described guidance will fail.