Skip to main content
Glama

Nathan AI Global Bounties

search_bounties

Read-only

Search source-checked mathematics prizes and science challenges.

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

Input Schema

NameRequiredDescriptionDefault
qNo
limitNo
statusNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/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 only the phrase "source-checked" about data provenance; it says nothing about pagination, default ordering, default limit, whether all filters combine conjunctively, or how large result sets behave.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single twelve-word sentence with no filler or redundancy, which is structurally clean. However, that brevity comes at the cost of under-specification rather than being genuinely economical.

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

Completeness2/5

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

Four optional parameters, zero schema descriptions, and no output schema means the description is the only place semantics could be explained, and it explains none of them. For a search tool where filter interaction and result volume matter, an agent is left guessing how to call it correctly.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning and largely fails to: q, limit, and status are never mentioned. The phrase "mathematics prizes and science challenges" loosely gestures at the category enum values, and the two enums are self-documenting, but the free-text query and limit semantics remain unexplained.

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

Purpose4/5

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

"Search" supplies a specific verb and the object ("mathematics prizes and science challenges") names the resource domain, so an agent knows this is a discovery/listing tool rather than a stats tool. The only weakness is that it never explicitly contrasts itself with the sibling get_prize_stats, though the verb difference carries most of the distinction.

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 guidance, no prerequisites, and no mention of when a different tool should be preferred. The word "Search" implies retrieval, but nothing tells the agent whether this is for browsing, exact lookup, or filtered exploration.

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.