Skip to main content
Glama

motogp_circuit_poles

Read-only

Get one MotoGP circuit's native pole-position frequencies and return every rider row with times, rider identity/link, 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. Empty MotoE data can be valid even when native pagination totals are nonzero, and no new rank or alias is synthesized.

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_poles"
  }
}

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.9/5.0
Behavior4/5

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

Beyond readOnlyHint and openWorldHint, it discloses meaningful quirks: empty MotoE results can be legitimate despite nonzero native pagination totals, and no rank or alias is synthesized from the source data. Those caveats materially change how an agent interprets the response, though permissions/rate-limit context is absent.

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 purpose in the first sentence and constraints after, with no filler. Slight redundancy in repeating the 'no alias synthesized' namespace warning already present in the schema.

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's summary of the returned rows and pagination object is bonus context rather than a necessity. It covers inputs, quirks, and output shape adequately for a two-parameter read tool, with only the sibling-selection rationale 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 both schema fields already explain the required UUID provenance and the category enum, so the description mostly restates that (required, source namespace, four category names). Baseline 3 applies since the schema carries the parameter detail.

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 specific verb and resource ('Get one MotoGP circuit's native pole-position frequencies') plus the row-level payload it returns, which cleanly separates it from sibling stats tools like motogp_circuit_wins and motogp_circuit_records without naming them.

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?

The description gives prerequisites (circuit_uuid must come from the result event's circuit.id; category_name must be one of the four lowercase names) but never states when to reach for this tool versus the wins/records siblings, so selection guidance is only implied by the resource 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.