Skip to main content
Glama

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

benchmarks_prize_attach

Idempotent

Author-only: declare a locked USDC prize on your benchmark (API key required). Poster-funded: this records the prize pending and never broadcasts; the response's poster_instructions list the wallet steps you sign. Needs a withdrawal_address on your owner account. Args: slug, amount_usdc, threshold_bps, payout_rule, closes_at, plus the optional BountyConfig fields. Returns the benchmark detail. REST twin: POST /api/v1/benchmarks/{slug}/prize. Custodial authors: benchmarks_prize_fund next.

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": {
      "amount_usdc": "<amount_usdc>",
      "threshold_bps": "<threshold_bps>",
      "payout_rule": "<payout_rule>",
      "closes_at": "<closes_at>"
    },
    "name": "benchmarks_prize_attach"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoBenchmark slug from benchmarks_list or benchmarks_search. Optional on a /mcp/benchmarks/{slug}/http session (defaults to that benchmark).
closes_atYesUTC moment prize locking ends.
entry_feeNoEntrant fee in USDC, pulled from each entrant's own wallet by enter() (0 = free entry; USDC has 6 decimals).0
splits_bpsNoWinner share per payout place in bps, frozen at creation (empty = operator-amounts mode). Non-empty splits GOVERN the award on-chain: at most splits_bps.length winners can be paid (TooManyWinners), and the platform must grant place i exactly pool * splits_bps[i] / 10_000 (SplitMismatch otherwise) — the payout_rule is metadata only in this mode. Each element is a non-zero place share of 1..10000; the cumulative sum must stay within 10000 — the remainder stays in the pool (a full 10000 sum is NOT required).
amount_usdcYesPrize pool in USDC. You lock it on-chain from your own wallet via the steps the attach response carries (the platform never funds bounties).
payout_ruleYeswinner_take_all: single winner takes the pool. top_n_split: top three split it 50/30/20. In frozen mode (non-empty splits_bps) this rule is METADATA ONLY on-chain: the frozen splits govern the payout shape, and the platform sizes every place from them.
max_entrantsNoEntrant cap (0 = uncapped; the on-chain width is a uint16 — 65535 max).
threshold_bpsYesScore threshold in basis points of the composite ceiling (0..10000; 8500 = a 0.8500 composite). Runs below it are not eligible for the prize.
claim_deadlineNoUTC deadline for winners to claim on-chain (default closes_at + 30d).
allowed_entrantsNoClosed entrant set as checksummed 0x addresses (empty = open entry).
grading_grace_secondsNoPost-close grading grace in seconds (0 = the v1 reclaim race preserved). Non-zero must fit inside the claim window: grading_grace_seconds <= claim_deadline - closes_at.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true), the description discloses that this records the prize as pending and does not broadcast, that the response carries poster_instructions with wallet steps the caller must sign, and that the platform never funds bounties. That is exactly the mutation semantics an agent needs before calling.

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 author-only constraint and the pending/no-broadcast behavior, then prerequisites, then args. Dense and mostly waste-free; the bare 'Args:' enumeration is mildly redundant given a fully documented schema.

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 an 11-parameter mutation with no output schema, the description covers who may call it, what it requires, what it does not do, what the response contains ('Returns the benchmark detail', poster_instructions), and the next step. Nothing essential 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 schema descriptions are already detailed (splits_bps governance rules, payout_rule frozen-mode caveat). The description only enumerates the required arg names plus 'the optional BountyConfig fields', adding no meaning beyond the schema, so 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?

A specific verb+resource ('declare a locked USDC prize on your benchmark') with scope qualifiers (author-only, API key required). It distinguishes itself from the neighboring life-cycle tools by naming benchmarks_prize_fund as the custodial path and stating this one 'never broadcasts'.

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?

Explicit preconditions are given (API key, withdrawal_address on the owner account) along with the branch that selects an alternative: 'Custodial authors: benchmarks_prize_fund next.' The agent knows both when to call it and where to route instead.

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