Skip to main content
Glama

Nathan AI Global Bounties

get_prize_stats

Read-only

Count open records and report prize and pool amounts separately.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that results are split into prize and pool amounts and that only 'open' records are counted, which is genuine behavioral context. It does not disclose the return shape, whether counts are aggregated or per-record, or what 'open' means, so it stops short of rich disclosure.

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?

A single front-loaded sentence with no filler; both verbs and both reported amounts appear immediately. The only cost is that its brevity leaves ambiguity unresolved rather than being over-wordy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters and no output schema, the description carries the entire burden of explaining what comes back, yet it only names two amount categories. Terms like 'open records' and 'pool' are never defined, which for a zero-input aggregate tool leaves the agent guessing at the returned fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so parameter semantics carry no burden and the baseline of 4 applies. There is nothing the description could add or omit regarding inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states two concrete actions ('Count' and 'report') and two outputs (prize and pool amounts), which is more specific than the name alone. But the resource is left vague: 'open records' is undefined, and it is unclear whether this is README bounties, prize claims, or something else. An agent can guess it is a stats counterpart to search_bounties, but the object being counted is never named.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. The description does not reference the sibling search_bounties or explain that this tool should be preferred for aggregate counts versus per-record retrieval. Usage is only inferable from the word 'stats' in the tool name.

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.