Skip to main content
Glama

Crawlora MCP

motogp_world_standings

Read-only

Get one native MotoGP v2 world-standings document for one result-season/category UUID pair and team or constructor entity. type is required (team or constructor), season_uuid comes from motogp_seasons and category_uuid from motogp_categories for the same season; calendar years, content-event UUIDs and category labels are rejected. Every returned row season/category/year is validated, source positions, ordering, fractional points, event/session context, report links and the official flag are preserved, and a native null classification stays null. No table, rank or points are computed and report links are not downloaded.

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

Input Schema

NameRequiredDescriptionDefault
typeYesNative standings entity. Documented values: team, constructor.
season_uuidYesResult-season UUID from seasons discovery
category_uuidYesResult-category UUID from categories for the same season

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

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the real burden and does: row-level validation of season/category/year, preservation of source positions, ordering, fractional points, event/session context, report links and the official flag, and that a native null classification stays null. It also discloses negative behavior — no table/rank/points computation and report links not downloaded — which is exactly the context an agent needs to avoid misinterpreting the output.

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?

Front-loaded with the purpose and then packed with constraint and behavior detail; nearly every clause adds information. It is a single dense block with long comma-chained lists, which costs a little scannability but not substance.

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?

An output schema exists, so return-value explanation is unnecessary, and the description still covers input provenance, rejection rules, validation and preservation guarantees, and non-computation. For a three-required-parameter read tool this leaves nothing an agent needs 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; the description adds value by restating that type is required and enumerating the accepted values (team, constructor) plus the rejection rules for season_uuid and category_uuid, including the 'same season' pairing constraint that the schema does not state.

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?

States a specific verb and resource: 'Get one native MotoGP v2 world-standings document' scoped to a result-season/category UUID pair and a team/constructor entity. The phrase 'native ... document' plus 'No table, rank or points are computed' distinguishes it from computed-standings siblings like motogp_standings without the agent opening a schema.

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?

Gives concrete prerequisites and provenance: season_uuid comes from motogp_seasons and category_uuid from motogp_categories for the same season, and it explicitly lists rejected inputs (calendar years, content-event UUIDs, category labels). It stops short of naming a sibling alternative for computed tables, so routing is implied rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources