Crawlora MCP

motogp_sessions

Read-only

List the sessions of one MotoGP event/category pair and return each session's native result UUID, type, number, date, circuit context, condition and report links, with sprint sessions kept as their own native record. event_uuid (from motogp_events) and category_uuid (from motogp_categories) are both required, and a valid pair can legitimately have no sessions. Use the returned session UUID with motogp_classifications; FINISHED, CANCELLED and NOT-STARTED records are returned without fabricating results.

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": {
      "event_uuid": "<event_uuid>",
      "category_uuid": "<category_uuid>"
    },
    "name": "motogp_sessions"
  }
}

Input Schema

Name	Required	Description	Default
`event_uuid`	Yes	Required result-event UUID from motogp_events. Valid event/category pairs can legitimately have no sessions.
`category_uuid`	Yes	Required result-category UUID from motogp_categories.

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.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: empty results are normal, and FINISHED/CANCELLED/NOT-STARTED sessions are returned as-is without fabricating results. It still says nothing about pagination, ordering, or rate limits.

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 scope statement is front-loaded and the guidance sentences follow logically with no filler. It is dense – several ideas packed into two long sentences – but essentially every clause carries information an agent needs.

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 two-parameter read tool with an output schema, full schema coverage, and annotations, this is complete: both inputs are sourced, the empty-result case is flagged, the downstream tool is named, and non-happy-path record states are described. Nothing required to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds provenance ('event_uuid from motogp_events', 'category_uuid from motogp_categories') and the crucial semantic that the pair is jointly valid and may yield zero sessions. That is meaningful added meaning beyond the schema's type declarations.

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?

The description opens with a specific verb and resource ('List the sessions of one MotoGP event/category pair') and enumerates what each record carries (UUID, type, number, date, circuit context, condition, report links). The clause about sprint sessions being their own native record further pins down scope so an agent can distinguish this from a latest-session or live-session sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains where the two required IDs come from ('from motogp_events' / 'from motogp_categories') and routes the agent forward ('Use the returned session UUID with motogp_classifications'). It also warns that a valid pair may legitimately return no sessions. It does not state when to prefer this over a most-recent-session alternative, but the usage context is nonetheless clear.

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.