Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

motogp_seasons

Read-only

List the complete native MotoGP result-season discovery catalog and return every season's result UUID, display name, year and current flag, preserving historical categories and test events. Takes no input; use this first to get the season_uuid that motogp_events, motogp_categories and the standings tools require. Result, broadcast and rider-directory UUIDs are distinct namespaces, and no season is invented from a calendar guess.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "motogp_seasons"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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

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

Annotations already declare readOnlyHint and openWorldHint, so the description is free to add real value: it guarantees the catalog is complete (historical categories, test events included) and warns that no season is fabricated from a calendar guess, which tells the agent to trust the list as authoritative. It also flags that result, broadcast and rider-directory UUIDs live in distinct namespaces, preventing cross-namespace misuse. No pagination or size limits are mentioned, keeping it from a 5.

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?

Three sentences, each carrying a distinct payload: what is returned, when to call it, and the namespace/provenance caveats. It is front-loaded with the purpose, though the phrasing is dense and slightly awkward ("no season is invented from a calendar guess"), which costs a point.

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 elaboration, and the description still names the key fields for orientation. It covers purpose, call ordering, identity of dependents, and data-integrity caveats — everything an agent needs for a zero-parameter discovery tool.

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?

Zero parameters, so the baseline is 4; the description only needs to confirm the tool is argument-free, which it does with "Takes no input." Nothing further can be added on the parameter side.

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 ("List the complete native MotoGP result-season discovery catalog") and enumerates the returned fields (result UUID, display name, year, current flag). It also names the sibling tools it feeds (motogp_events, motogp_categories, standings tools), so an agent can place it precisely in the tool graph.

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?

"use this first to get the season_uuid that motogp_events, motogp_categories and the standings tools require" gives an explicit ordering rule and names the downstream consumers. "Takes no input" removes any doubt about prerequisites or required arguments.

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