Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

motogp_content_events

Read-only

Read the complete native public MotoGP content event catalog for one season year and return all source event metadata in native order: GP, test and media-event timing records with venue/track context, category relations, schedule options, broadcasts and availability flags. season_year is required. Assets, playback, client location and venue narratives are excluded; there are no server-side kind or date filters, and a season can include preseason dates in the preceding calendar year.

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_content_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
season_yearYesRequired four-digit source season year, for example 2026. Source season years can include preseason dates in the preceding calendar year.

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

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnlyHint and openWorldHint, and the description adds meaningful behavior on top: results arrive in native source order, no server-side filtering is applied, and a season may include preseason dates in the preceding calendar year. It does not discuss result volume or pagination for what is described as a complete catalog, which is the main remaining gap.

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 lead clause is front-loaded with the core action and scope, and every clause carries information (return shape, exclusions, filter behavior, date caveat). The enumerated record list is dense and makes the description a single long run-on sentence, but nothing is genuinely wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't document return fields, yet it still sketches the record types it returns and states the exclusion boundary, which is enough to call the tool correctly. The absence of any note on response size or paging for a full-season catalog is a modest omission given the scope.

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% and the single season_year parameter already documents 'four-digit source season year' and the preseason caveat, so the description's repetition of 'season_year is required' and the preceding-calendar-year note adds little new meaning. Baseline 3 is appropriate when the schema carries the parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Read the complete native public MotoGP content event catalog') and pins the scope to one season year, returning event timing records with venue/track context. An agent can distinguish it from the singular-looking sibling motogp_content_event by the 'complete catalog' framing, though no sibling is named explicitly.

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 states the required input and rules out server-side kind or date filtering, plus explicitly excludes assets, playback, client location and venue narratives, which is real scope guidance. However, it never says when to prefer this over the more targeted siblings such as motogp_content_event, motogp_events or motogp_sessions, so the choice is left to inference.

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