Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

motogp_classifications

Retrieve native MotoGP session classifications by result UUID, including historical and test events with source-native fields for accurate race results.

Instructions

Get a native MotoGP session classification. Reads anonymous MotoGP results metadata using the result UUID namespace. Historical categories and test events retain their native source fields.

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": {
      "session_uuid": "<session_uuid>"
    },
    "name": "motogp_classifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
testNoNative test-session flag; defaults to false
session_uuidYesResult UUID from the corresponding discovery resource

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description does carry some of the burden: 'anonymous' signals no auth is needed and 'Reads' signals a read-only operation. However, it says nothing about error behavior for an invalid UUID, the shape of the returned classification, or how the 'test' flag changes the result beyond a passing mention of native source fields.

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?

The purpose is front-loaded in a single clean sentence, but the second sentence ('Historical categories and test events retain their native source fields') is opaque and does not clearly earn its place for an agent that has not seen the data model.

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?

There is no output schema, so the description must convey what a 'classification' contains, yet it never indicates that results are rider positions/times/points or how they are ordered. For a simple two-parameter read tool the gaps are survivable, but the agent is left guessing at the return payload.

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%, so both parameters are already documented in the schema, which sets the baseline at 3. The description adds only marginal meaning, echoing the UUID namespace concept and alluding to test sessions without clarifying how the 'test' flag affects returned fields.

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 ('Get') and a specific resource ('native MotoGP session classification') scoped to a session, which distinguishes it from standings, starting_grid and sessions siblings. It stops short of explicitly contrasting with the nearest alternative, and 'classification' is jargon an agent may not map cleanly to 'results'.

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 statement of when to use this versus motogp_standings, motogp_starting_grid, or motogp_latest_session, and no exclusions. The only hint of usage context is the vague phrase 'result UUID namespace', which does not tell the agent under what conditions this tool is the right choice.

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