Skip to main content
Glama

motogp_circuit_wins

Read-only

Get one MotoGP circuit's native first-place frequencies and return every rider row with times, rider identity/link, finishing position 1, source order and the native pagination object. circuit_uuid is required and comes from the result event's circuit.id; category_name is required and is one of motogp, moto2, moto3 or motoe. Broadcast event UUIDs, result event UUIDs, rider UUIDs and numeric legacy IDs are different namespaces, and no rank or historical alias is calculated.

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": {
      "circuit_uuid": "<circuit_uuid>",
      "category_name": "<category_name>"
    },
    "name": "motogp_circuit_wins"
  }
}

Input Schema

NameRequiredDescriptionDefault
circuit_uuidYesRequired result-circuit UUID from the circuit context in motogp_events or a session payload, for example e9a71399-cea9-400a-b2ef-48bfdcdf6526. Use the result event's circuit.id; broadcast event UUIDs, result event UUIDs and rider UUIDs are different namespaces.
category_nameYesRequired circuit-statistics category name, one of: motogp, moto2, moto3, motoe. These lowercase names are a separate namespace from result-category UUIDs and historical classification labels; no historical alias is synthesized.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries real weight and delivers: full row contents, source ordering, the pagination object, and an explicit negative constraint that no rank or historical alias is calculated. The namespace warning about broadcast/result/rider UUIDs is genuinely useful disambiguation beyond safety hints.

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?

Purpose is front-loaded, but the second half is a dense run-on mixing return shape, input requirements and namespace caveats in one breath. The namespace warning is repeated from the schema, costing space without new information.

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?

An output schema exists, so the description needn't explain returns, yet it still sketches the row shape. Combined with input sourcing rules and the negative constraint on rank/alias, an agent has what it needs to call this correctly; the only gap is comparative guidance against sibling circuit tools.

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%, so both parameters are already documented with sourcing guidance and enum values. The description largely restates the same required-ness and namespace caveats rather than adding new meaning, so baseline 3 applies.

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?

States a specific verb and resource ('Get one MotoGP circuit's native first-place frequencies') and specifies the returned grain (every rider row with times, identity, finishing position, source order, pagination). 'First-place frequencies' implicitly separates it from poles/records siblings, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Gives input sourcing rules (circuit_uuid comes from the result event's circuit.id; category_name is one of four lowercase names) but never states when to prefer this over motogp_circuit_poles, motogp_circuit_records, or motogp_classifications, nor any when-not condition. Usage is implied by the resource name only.

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.