Skip to main content
Glama

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

benchmark_commit_bank

Author-only: commit this benchmark's task bank under a salted Merkle root (API key required; the author is your key). One bank, one root: once anchored on-chain a repeat is a conflict carrying the root. Arg: slug (defaults to the routed benchmark). Returns benchmark_slug, merkle_root, leaf_count, anchor_status, tx_hash, chain_id, committed_at. REST twin: POST /api/v1/benchmarks/{slug}/commit. Next: benchmark_commitment.

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_commit_bank"
  }
}

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
Behavior5/5

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

Annotations already flag readOnlyHint=false, idempotentHint=false, and openWorldHint=true; the description goes beyond them by explaining WHY non-idempotency holds (one bank, one root; a repeat is a conflict carrying the root) and by disclosing that the write is anchored on-chain. It also flags the auth requirement and enumerates the returned fields, which matters since no output schema exists.

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 audience gate, then the core semantics, then arg, return fields, REST twin, and next step — no filler sentences. The telegraphic phrasing ('One bank, one root') is compact but demands a second read to parse the conflict rule.

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?

For a state-changing, on-chain-anchored tool with no output schema, the description supplies the missing pieces an agent needs: auth requirement, conflict-on-repeat semantics, the full return field list, and the REST equivalent. Nothing material is left to inference.

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 there is only one parameter, so the schema already documents slug, its default, and the /mcp/benchmarks/{slug}/http routing behavior. The description restates 'slug (defaults to the routed benchmark)' without adding format or validation meaning beyond what the schema provides.

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 ('commit this benchmark's task bank under a salted Merkle root') plus a clear audience constraint ('Author-only'), which separates it from read-side siblings like benchmark_corpus or benchmark_commitment. An agent can tell exactly what the tool does without opening the 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?

Names the precondition ('API key required; the author is your key'), the exclusivity rule ('One bank, one root: once anchored on-chain a repeat is a conflict carrying the root'), and routes to the next step ('Next: benchmark_commitment'). It does not enumerate an explicit alternative when the caller is not the author, but the author-only gate makes the exclusion implicit.

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