Skip to main content
Glama

Propose a new race

propose_race

Send a US ultramarathon the index does not have yet. Check with search_races first. quote is copied verbatim from source_url and names the race. One call for each distance (a 50K and a 100M at the same event are two races). Give the two-letter state. A verified race that is not listed is added at once and a research agent gathers its values next; one that looks like a listed race is held for a maintainer.

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": {
      "name": "<name>",
      "distance_category": "<distance_category>",
      "source_url": "<source_url>",
      "quote": "<quote>"
    },
    "name": "propose_race"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
nameYes
quoteYes
stateNo
source_urlYes
website_urlNo
distance_categoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by describing the post-call lifecycle: a verified unlisted race is added immediately and a research agent fills in its values, while a race resembling a listed one is queued for a maintainer. Annotations only say non-read-only, non-idempotent and open-world; this adds the actual consequence of the write.

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?

Dense and front-loaded: the prerequisite and the per-distance rule come before the lifecycle detail. The phrasing is terse to the point of fragmentary ('Send a US ultramarathon the index does not have yet'), but no sentence is wasted.

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

Completeness4/5

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

For a 7-parameter, non-idempotent write tool with no output schema, the description covers the key risk (duplicates get held), the immediate outcome, and the trickiest field semantics. What remains thin is guidance on the four optional/locational fields, which neither schema nor description explains.

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?

With 0% schema coverage the description must carry the burden, and it explains the two most error-prone fields: `quote` must be copied verbatim from `source_url` and must name the race, and `state` must be two letters. `city`, `website_url` and `name` are left unstated, so compensation is strong but incomplete.

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: send a US ultramarathon the index lacks. The scope words 'US' and 'the index does not have yet' separate it cleanly from search_races and propose_correction, so an agent can pick it without opening a 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 an explicit prerequisite ('Check with search_races first') and a segmentation rule ('one call for each distance') with a concrete 50K/100M example. The only gap is an explicit statement of the duplicate case being a reason not to call, though the maintainer-hold clause implies it.

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