Skip to main content
Glama

Crawlora MCP

motogp_bmw_award

Read-only

Get the native BMW Award classification table for one calendar season year and return every row with position, points, rider identity, constructor, team and event context, plus the source report link. season_year is a required four-digit numeric year from motogp_seasons, not a season UUID. An empty classification is a valid source result and does not establish that the award existed that season; no report document is fetched.

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_year": "<season_year>"
    },
    "name": "motogp_bmw_award"
  }
}

Input Schema

NameRequiredDescriptionDefault
season_yearYesRequired four-digit calendar season year, for example 2026. This is the numeric year from motogp_seasons, not a season UUID; an empty classification does not mean the award did not exist that 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.2/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial context beyond that: the exact row shape returned, that an empty classification is a valid source result rather than evidence the award did not exist, and that no report document is fetched. These are real behavioral caveats an agent would otherwise get wrong when reporting 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?

Two sentences, front-loaded with verb and resource, with the interpretive caveat trailing where it belongs. It is dense but every clause carries information; the only minor waste is repeating the parameter caveat that the schema already contains.

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 single-parameter, read-only lookup with an output schema and full schema coverage, the description covers purpose, input sourcing, return contents, and the key interpretive pitfall. Nothing an agent needs to invoke and report this correctly 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% and the schema already spells out the four-digit year, the not-a-UUID rule, and the empty-classification caveat. The description restates the same facts almost verbatim in its own sentence, so it adds no meaning the schema does not already carry; 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 opens with a specific verb and resource ("Get the native BMW Award classification table") and scopes it to "one calendar season year." It also enumerates the returned fields (position, points, rider, constructor, team, event context, source report link), so an agent can tell this apart from general classifications or standings siblings without opening the schema.

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 useful prerequisite by pointing at motogp_seasons as the source of the season_year value, and it warns how not to interpret an empty result. However, it never states when to prefer this over alternatives such as motogp_classifications or motogp_standings, so the usage boundary is only implied.

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