Skip to main content
Glama

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

benchmarks_prize_award

Author-only: award this benchmark's funded prize from its scored runs (API key required). Winners are computed server-side and paid to their owners' withdrawal addresses by the contract. Not callable before the prize closes; a repeat is a conflict. A failed broadcast returns awarded=false with the prize still funded. Arg: slug. Returns awarded, award_tx, bounty_status, payout_rule, winners, total_usdc, note. REST twin: POST /api/v1/benchmarks/{slug}/award.

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

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?

Adds substantial context beyond the annotations: API key requirement, server-side winner computation, payment to owners' withdrawal addresses by the contract, and the failure semantics ('a failed broadcast returns awarded=false with the prize still funded'). The 'a repeat is a conflict' note sharpens the non-idempotent annotation into a concrete operator expectation.

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 author-only framing and scope, and every clause carries a distinct fact (auth, computation, payment, failure mode, return fields, REST twin). The telegraphic 'Arg: slug' fragment and trailing field list are compact but slightly list-like rather than prose.

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 enumerates the return fields (awarded, award_tx, bounty_status, payout_rule, winners, total_usdc, note) and covers the failure shape, so an agent knows both what it gets back and how to interpret a false award.

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 field already documents its source tools and session-default behavior, so the description's 'Arg: slug' adds nothing new. Per the baseline rule for fully documented single-parameter schemas, this lands at 3.

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 ('award this benchmark's funded prize from its scored runs') plus the actor restriction ('Author-only'), and clarifies that winners are computed server-side rather than supplied by the caller. This distinguishes it cleanly from siblings like benchmarks_prize_fund, benchmarks_prize_attach, and benchmarks_prize_reclaim.

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 explicit preconditions and exclusions: not callable before the prize closes, and a repeat call is a conflict. It does not name an alternative tool for the adjacent steps (funding, attaching, reclaiming), leaving the agent to infer sibling roles from names alone.

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