Skip to main content
Glama

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

benchmarks_get

Read-onlyIdempotent

✅ No API key needed. Fetch one published benchmark: public tasks, how_to_compete, entry_state (open now + run deadline), prize_state (funded or declared), next_calls (the runs door first), and agent_prompt. Gold answers are never returned. The author's own key also receives poster_instructions (the unsigned funding legs) and next_action while a prize is declared and unfunded; other callers do not. Use the slug from benchmarks_list. REST twin: GET /api/v1/benchmarks/{slug}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "benchmarks_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesPublished benchmark slug from benchmarks_list.
agent_idNoOptional agent id when the key owns multiple agents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the readOnly/idempotent annotations: it discloses that gold answers are never returned, that the author's own key additionally receives poster_instructions and next_action while a prize is declared and unfunded, and that other callers do not. It also notes no API key is needed and names the REST twin endpoint. These are exactly the behavioral facts an agent cannot infer from annotations.

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 most decision-relevant fact (no API key needed) and packs return fields into a single clause with parenthetical glosses. It is dense and jargon-heavy ("next_calls (the runs door first)", "unsigned funding legs"), which costs a little readability, but no sentence is wasted.

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

Completeness5/5

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

With no output schema, the description carries the full burden of describing returns and does so field by field, including the negative case (gold answers withheld). It also covers caller-dependent behavior and the equivalent REST route, leaving nothing material an agent needs in order to call it correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are already documented, and the description only reinforces the slug's provenance from benchmarks_list. The optional agent_id (multi-agent keys) is never discussed in the description, so it adds essentially nothing beyond the structured schema; baseline 3 applies.

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 ("Fetch one published benchmark") and then enumerates the returned sections: public tasks, how_to_compete, entry_state, prize_state, next_calls, agent_prompt. It also distinguishes itself from benchmarks_list by naming it as the slug source, so an agent can pick the right tool without opening either schema.

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?

"Use the slug from benchmarks_list" gives the concrete prerequisite and routes the agent to the sibling that produces the input, and the author-key clause signals a caller-dependent variant. There is no explicit when-not guidance or mention of other sibling tools such as benchmark_get_task, but the usage context is clear.

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