Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

motogp_classifications

Read-only

Get one MotoGP session classification and return the session identity plus every rider row with native position, rider identity, team, bike, timing and status fields. session_uuid is required and comes from motogp_sessions; test is the source's own test-session flag and defaults to false. A finished historical session can legitimately have an empty classification, and practice/test rows carry different fields from race/sprint rows.

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
testNoOptional native test-session flag; defaults to false. A finished historical session can legitimately have an empty classification.
session_uuidYesRequired result-session UUID from motogp_sessions, for example 656efa33-5c39-4d93-b8ef-8b669fdbec05.

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

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

The annotations already establish read-only and open-world behavior, and the description adds meaningful context beyond them: finished historical sessions can legitimately return an empty classification, and practice/test rows have different fields from race/sprint rows. It does not discuss permissions or rate limits, but the key data-variability behavior is disclosed.

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 three sentences, front-loads the main purpose, and places edge cases afterward. It is efficient overall, though parts of the parameter guidance repeat what the schema already states.

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?

For a two-parameter, read-only tool with an output schema and annotations, the description covers the core purpose, prerequisite source, default flag behavior, and important empty-result and row-type caveats. It could be stronger with explicit sibling guidance, but nothing essential for correct invocation is 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 description coverage is 100%, so both parameters are already documented in the schema. The description reinforces that session_uuid is required and sourced from motogp_sessions, and that test defaults to false, but it does not add syntax or meaning beyond the schema.

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 uses a specific verb, 'Get,' and a specific resource, 'one MotoGP session classification,' and defines the returned rider-row scope and fields. It implies the relationship to motogp_sessions as the source of session_uuid, but it does not explicitly differentiate this tool from other classification-like siblings.

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?

It gives a clear prerequisite that session_uuid comes from motogp_sessions and explains the test flag default. However, it does not explicitly state when to use this tool instead of alternatives such as starting-grid or entry tools, so usage guidance is implied rather than complete.

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

All Crawlora MCP toolsInspect
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.

Resources