Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

motogp_circuit_records

Retrieves native MotoGP circuit record metadata by circuit UUID while preserving result UUID namespaces and source report/record variants.

Instructions

Get native circuit record metadata. Reads anonymous native result metadata. Result UUID namespaces and source report/record variants are preserved.

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

NameRequiredDescriptionDefault
circuit_uuidYesResult UUID from the corresponding discovery resource

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

C2.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does contribute real behavioral context: reads are anonymous (no auth), and result UUID namespaces plus source report/record variants are preserved, implying stable identifiers. However it never says what the payload contains, whether it is paginated, or how large it may be.

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?

Three short sentences, but the first two are largely redundant ("native circuit record metadata" vs "native result metadata") and the third is dense jargon about namespaces and report variants without explanation. It is front-loaded but not information-dense.

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?

For a single-parameter tool with no output schema and no annotations, the description should explain what the returned metadata looks like. Instead it leaves the return shape entirely opaque and gives no guidance on the relationship to the "discovery resource" that supplies the UUID.

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 coverage is 100% and the schema already documents circuit_uuid as a "Result UUID from the corresponding discovery resource." The description's mention of "Result UUID namespaces" loosely reinforces this but adds no new meaning, and it does not explain how to obtain the UUID beyond what the schema says.

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

Purpose3/5

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

"Get native circuit record metadata" names a verb and a resource, but "records" and "metadata" are vague about what is actually returned (lap records? all-time results?). It does not distinguish itself from sibling tools like motogp_circuit_poles or motogp_circuit_wins, so an agent cannot tell which circuit-record tool to pick from the description alone.

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 mention of prerequisites, and no reference to alternatives. The sentence "Reads anonymous native result metadata" hints only that no authentication is needed, not when this tool should be selected over the circuit poles/wins siblings.

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

Deploy Server

Other Tools