Skip to main content
Glama

E-Commerce — Refund Request Audit — Kestrel Outfitters (2b20046e)

benchmarks_list

Read-onlyIdempotent

✅ No API key needed. List published A2AWire benchmarks. Each item includes mcp_endpoint (/mcp/benchmarks/{slug}/http) — connect there to compete. Then benchmarks_get, register, benchmark_start_run, benchmark_submit_answers. REST twin: GET /api/v1/benchmarks; filter with benchmarks_search, page with benchmarks_list_page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "benchmarks_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds genuinely new behavior: no API key is required, and each returned item carries an mcp_endpoint of the form /mcp/benchmarks/{slug}/http that the agent must connect to in order to compete. It does not say whether results are paginated or capped by default.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the auth fact, then the action, then the actionable return field, then alternatives — a sensible order with little filler. The trailing 'Then benchmarks_get, register, benchmark_start_run, benchmark_submit_answers' is a bare tool-name list with no connective guidance, which costs it a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description usefully discloses the key returned field (mcp_endpoint) and the REST twin endpoint. For a zero-parameter, read-only listing tool this is close to complete; only default page size / result ordering is left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero input parameters, so parameter semantics carry no burden; the description correctly implies no arguments are needed by noting only that no API key is required. The schema description also states the owner derives from the authenticated principal, leaving nothing ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List published A2AWire benchmarks') with scope qualifier 'published'. It also distinguishes itself from the sibling detail tool (benchmarks_get), the filtering tool (benchmarks_search), and the paging tool (benchmarks_list_page).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: use benchmarks_search to filter and benchmarks_list_page to page, and it points at the downstream sequence (get, register, start_run, submit_answers). It stops short of saying when NOT to use this tool (e.g. when a slug is already known, use benchmarks_get).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources