Skip to main content
Glama

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

benchmark_commitment

Read-onlyIdempotent

✅ No API key needed. Read a benchmark bank's public commitment. Use it to check the salted Merkle root a receipt's commit_root points at. Arg: slug (defaults to the routed benchmark). Returns merkle_root, leaf_count, anchor_status, tx_hash, anchor_block, chain_id, contract_address and committed_at; salts and gold never appear. Not found until the author commits. Keyless and keyed calls get the same body. REST twin: GET /api/v1/benchmarks/{slug}/commitment. Next: benchmark_run_receipt to match a run's commit_root.

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": "benchmark_commitment"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoBenchmark slug from benchmarks_list or benchmarks_search. Optional on a /mcp/benchmarks/{slug}/http session (defaults to that benchmark).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: no API key is required, keyless and keyed calls return the same body, and salts/gold are never exposed. It does not mention rate limits or pagination, but for a single-object lookup that is minor.

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-loaded with the keyless-access fact, then purpose, argument, return fields and next step — a sensible priority order for a dense, information-rich definition. The leading checkmark emoji is cosmetic noise and the return-field list is long, but it earns its space since no output schema exists.

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 compensates by enumerating every returned field (merkle_root, leaf_count, anchor_status, tx_hash, anchor_block, chain_id, contract_address, committed_at) and by stating what is withheld (salts, gold). It also gives the REST twin endpoint, so an agent has everything needed to call and interpret this 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 single slug parameter is fully documented in the schema, including its routed-benchmark default. The description's 'Arg: slug (defaults to the routed benchmark)' only restates the schema default rather than adding format or edge-case meaning, 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?

The description opens with a specific verb and resource: 'Read a benchmark bank's public commitment,' then narrows it further with the concrete use case of verifying the salted Merkle root a receipt's commit_root points at. An agent can distinguish this from benchmark_commit_bank (writing) and benchmark_run_receipt (matching) without opening any schema.

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

Usage Guidelines5/5

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

It states exactly when to call it ('Use it to check the salted Merkle root a receipt's commit_root points at') and explicitly names the follow-up tool, benchmark_run_receipt, for matching a run's commit_root. It also warns about the failure condition — 'Not found until the author commits' — so the agent knows what an empty result means.

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