Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

motogp_content_events

Retrieves MotoGP content events for a given season year, returning GP, test and media-event timing metadata with venue, track, category and availability context.

Instructions

Read MotoGP content event catalog. Returns all source event metadata in native order, including GP, test and media-event timing metadata. Preserves native schedules, season context, venue/track fields, category relations and availability flags. Assets, playback, client location and venue narrative content are excluded. Source season years can include preseason dates in the preceding calendar year. No locally computed filters, timezone transforms or pagination.

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_yearYesFour-digit source season year

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses native ordering, included metadata, excluded content, the preseason season-year nuance, and the absence of local filters, timezone transforms, or pagination. This is strong transparency for a read-only catalog tool.

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 purpose, and most sentences carry distinct scope or behavioral detail. The list of preserved fields and exclusions is dense, and 'native order'/'native schedules' overlap slightly, but the description is not padded.

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 no output schema and no annotations, the description must explain return content and operational constraints. It names included metadata categories, exclusions, native ordering, the season-year caveat, and no filtering/pagination. It lacks explicit response-shape detail such as array versus object, but is largely complete for a one-parameter catalog read.

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?

The sole parameter is documented at 100% in the schema, so the baseline is 3. The description adds useful semantic nuance: source season years may include preseason dates in the preceding calendar year. That meaningfully supplements the schema's 'Four-digit source season year'.

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?

States a specific verb and resource: read the MotoGP content event catalog, including GP, test, and media-event timing metadata. It also clarifies scope with exclusions for assets, playback, client location, and venue narrative content. It does not explicitly distinguish this from the singular motogp_content_event or motogp_events, so it is not a 5.

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?

Usage is implied by the catalog/read framing and the exclusion list, but there is no explicit 'use this when...' guidance or named alternative. It does not tell the agent when to choose motogp_content_event instead of this catalog. The implied context is adequate but has clear gaps.

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

Deploy Server

Other Tools