Crawlora MCP

motogp_standings_files

Read-only

List one MotoGP championship's standings report links and return the native riders_results and riders_championship report-link groups with their published URLs. season_uuid and category_uuid are both required and come from motogp_seasons and motogp_categories. Source empty URLs stay empty, a menu key alone does not establish a published report, and no linked document is fetched; use motogp_standings for the actual standings values.

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": {
      "season_uuid": "<season_uuid>",
      "category_uuid": "<category_uuid>"
    },
    "name": "motogp_standings_files"
  }
}

Input Schema

Name	Required	Description	Default
`season_uuid`	Yes	Required result-season UUID from motogp_seasons.
`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.6/5.0

Behavior5/5

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

Annotations already mark this as a read-only, open-world operation, and the description goes well beyond them: it declares that no linked document is fetched, that source-empty URLs stay empty, and that a menu key alone does not establish a published report. Those are exactly the behavioral caveats an agent would otherwise get wrong when interpreting results.

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?

It is front-loaded with the purpose before the constraints and the sibling pointer, and every sentence carries information. The middle sentence is densely packed with three separate caveats, which slightly hurts readability but nothing is wasted.

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?

With an output schema present, return values need no explanation, and the description covers everything else: input provenance, the no-fetch behavior, how empty or menu-only URLs should be interpreted, and where to go for standings values. Nothing needed to call or interpret this tool 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 coverage is 100%, so both parameters are already fully documented, including their provenance from motogp_seasons and motogp_categories. The description restates that provenance and adds no additional syntax, format, or edge-case guidance for the parameters, so the baseline 3 applies.

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 names a specific verb (list/return) and resource (a MotoGP championship's standings report links), and it describes the exact payload shape (riders_results and riders_championship report-link groups with published URLs). It explicitly sets itself apart from motogp_standings, so an agent can choose between the two without inspecting schemas.

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

Usage Guidelines5/5

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

It states the precondition for the required inputs (season_uuid and category_uuid come from motogp_seasons and motogp_categories) and names the correct alternative for a different need (motogp_standings for actual standings values). Both when-to-use and when-not-to-use are explicit.

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.