Skip to main content
Glama

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

benchmark_run_receipt

Read-onlyIdempotent

✅ No API key needed. Fetch the public receipt of a finalized benchmark run. Use it to verify a score independently. Arg: run_id. Returns receipt_hash, the immutable payload (answer digests only), anchor evidence, basescan_tx_url, the bank commit_root and verify_hints; score_opening appears once the benchmark closes. Not found until the run is scored. Keyless and keyed calls get the same receipt. REST twin: GET /api/v1/benchmarks/runs/{run_id}/receipt. Next: benchmark_commitment.

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": {
      "run_id": "<run_id>"
    },
    "name": "benchmark_run_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesUUID of a finalized run (benchmark_my_runs lists yours).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: no API key required, keyless and keyed calls return the same receipt, the resource 404s until the run is scored, and score_opening appears only after close. These auth, error-state, and timing traits are exactly what an agent cannot infer from structured fields.

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 key constraint (no API key) and keeps every sentence functional. The returns enumeration is a dense clause chain that would read better as a short list, but nothing is redundant.

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 return-shape burden and does so by naming receipt_hash, digests, anchor evidence, basescan_tx_url, commit_root, and verify_hints. Auth model, failure condition, REST twin, and next step are all covered for a one-parameter read tool.

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 coverage is 100% and the schema already explains run_id is a UUID and points to benchmark_my_runs for discovery. The description's "Arg: run_id" adds no meaning beyond that, so the 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 the public receipt of a finalized benchmark run") with the scope qualifier "finalized" that separates it from result/commitment siblings. The added "Use it to verify a score independently" pins down intent rather than restating the name.

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?

Gives a clear use case (independent score verification), a hard precondition ("Not found until the run is scored"), and a follow-on route ("Next: benchmark_commitment"). It stops short of naming an alternative such as benchmark_get_results to say when not to use this one.

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