Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

motogp_content_event

Retrieve MotoGP content event metadata using a content-event UUID to get native event, category, venue, track, and schedule details plus result UUID bridges.

Instructions

Read MotoGP content event metadata. Uses a content-event UUID from the content catalog or session metadata. Returns the native public event/category/venue/track/schedule metadata and explicit result-event/result-circuit UUID bridges when present. Does not synthesize mappings or hydrate classifications. Preserves nulls, dates and source spelling; excludes assets, playback, client location and venue narratives.

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": {
      "id": "<id>"
    },
    "name": "motogp_content_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesContent-event UUID; not a result-event UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses that results are raw native metadata, that explicit result-event/result-circuit UUID bridges appear 'when present', and it explicitly rules out synthesizing mappings or hydrating classifications. It also scopes out assets, playback, client location and venue narratives, and promises null/date/spelling preservation. Missing only auth, rate-limit, and error behavior for a mutation-free read.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four compact sentences, front-loaded with the action and input, followed by return shape and then negative scoping. Every clause — including the exclusions — carries information an agent would otherwise have to guess; nothing is redundant.

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?

For a one-parameter read with no output schema, the definition covers input provenance, return contents, and edge cases (nulls, source spelling, absent bridges) adequately. It would be fully complete with a note on what happens for an unknown or non-content-event UUID.

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 schema already documents the single parameter at 100% coverage, so baseline would be 3. The description adds genuine meaning beyond the schema by stating where the content-event UUID can be sourced (content catalog or session metadata), which the schema's terse 'not a result-event UUID' note does not.

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 MotoGP content event metadata', and pins the identity to a 'content-event UUID'. It is clear what the tool returns, but it never contrasts itself with close siblings like motogp_content_events or motogp_events, leaving the agent to infer which one to call.

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?

The description implies usage by saying the UUID comes 'from the content catalog or session metadata', which tells the agent where the input originates. It gives no explicit when-to-use/when-not guidance and does not name an alternative tool for listing versus fetching a single event.

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