Crawlora MCP

motogp_circuit_records

Read-only

Get one MotoGP circuit's record metadata and return the requested circuit identity plus every returned class record group: top speed, fastest lap, best pole, circuit record and all most-wins and most-poles rows. circuit_uuid is required and comes from the circuit context in motogp_events or a session payload. Rider records may use name or full_name, namespaces are not combined, and no missing class or record 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>"
    },
    "name": "motogp_circuit_records"
  }
}

Input Schema

Name	Required	Description	Default
`circuit_uuid`	Yes	Required result-circuit UUID from the circuit context in motogp_events or a session payload, for example e9a71399-cea9-400a-b2ef-48bfdcdf6526. The circuit UUID namespace is distinct from broadcast and rider-directory IDs.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 2026

TDQS

A4/5.0

Behavior5/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, but the description adds substantive behavioral context beyond that. It specifies the full set of returned record groups, states that rider records may use name or full_name, clarifies that namespaces are not combined, and explicitly says no missing class or record is synthesized. Those are meaningful contract details for an agent interpreting or relying on the result.

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?

The description is appropriately sized and front-loads the core operation and returned record groups. The later sentences add useful constraints about UUID source, name fields, namespaces, and non-synthesis. There is minor repetition of the required UUID prerequisite already covered by the schema, but overall it is efficient.

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

Completeness5/5

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

For a single-parameter record lookup with an output schema and safety annotations, the description is complete enough to call correctly. It identifies the required UUID source, describes the returned record groups, and discloses important non-synthesis and namespace behavior. The output schema can carry detailed return-value structure, so the description does not need to explain every field.

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 description coverage is 100%, and the schema already documents circuit_uuid as the required result-circuit UUID from motogp_events or a session payload, including its distinct namespace. The description repeats the required/source information but adds no new format, validation, or example detail beyond the schema. Baseline 3 is appropriate when the schema carries the parameter documentation.

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?

The description states a specific verb and resource: get one MotoGP circuit's record metadata. It enumerates the returned record groups, including top speed, fastest lap, best pole, circuit record, most wins, and most poles, which helps distinguish it from narrower record tools. However, it does not explicitly name or contrast with siblings such as motogp_circuit_poles or motogp_circuit_wins.

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 a clear prerequisite: circuit_uuid is required and comes from the circuit context in motogp_events or a session payload. It does not state when to choose this comprehensive record tool over the sibling poles or wins tools, nor does it give exclusions. Usage is implied by the output scope rather than explicitly guided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.