Skip to main content
Glama

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

benchmarks_prize_reclaim

Idempotent

Author-only, platform-custodial wallets: return a closed, unawarded prize pool to its frozen on-chain author (API key required). Opens only after closes_at; self-custody authors are pointed at the on-chain reclaim(). A repeat after success signs nothing. Arg: slug. Returns the benchmark detail plus a reclaim block (status, reclaim_tx, failure, failure_code). REST twin: POST /api/v1/benchmarks/{slug}/prize/reclaim.

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

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 declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=true; the description adds the parts annotations cannot express: API-key requirement, author/platform-custodial eligibility, the closes_at gate, and the fact that a repeat after success signs nothing. It also names the return payload fields (status, reclaim_tx, failure, failure_code), which is behavior an agent needs to interpret outcomes.

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 eligibility scope, then the timing gate, the redirect, idempotency, and the return shape, in a compact block of sentences. Dense with useful facts, though the staccato clauses and parentheticals cost a little readability.

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 single-optional-param mutation with no output schema, the definition covers authentication, eligibility, timing, repeat-call behavior, the return block, and the REST equivalent. Nothing an agent needs in order to call it safely and interpret the result is missing.

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 slug parameter already documents the fallback to the routed benchmark session. The description's 'Arg: slug' repeats the schema without adding interpretation, 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 concrete verb and resource ('return a closed, unawarded prize pool to its frozen on-chain author') and immediately scopes it to author-only, platform-custodial wallets. That scope clause is what separates it from the sibling funding and award tools, so an agent can pick it correctly 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?

Gives real preconditions: only after closes_at, only for unawarded closed prizes, and only for platform-custodial authors, with self-custody authors redirected to the on-chain reclaim(). It stops short of naming an MCP sibling as the alternative route, but the when-to-use conditions are explicit.

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