Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

motogp_event_files

Retrieve native MotoGP event and category report links using event and category UUIDs, preserving source report and record variants for direct data access.

Instructions

Get native event and category report links. Reads anonymous native result metadata. Result UUID namespaces and source report/record variants are preserved.

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": {
      "event_uuid": "<event_uuid>",
      "category_uuid": "<category_uuid>"
    },
    "name": "motogp_event_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_uuidYesResult UUID from the corresponding discovery resource
category_uuidYesResult UUID from the corresponding discovery resource

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose two real traits: the read is anonymous (no auth implied) and UUID namespaces plus source report/record variants are preserved, indicating a passthrough rather than a normalized response. However, it never states the response shape, whether multiple links may be returned, or any rate/error behavior, so coverage is partial.

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 short sentences with no filler, and the core action is front-loaded. The remaining sentences are terse to the point of being cryptic jargon rather than wasteful, but structurally there is nothing to cut.

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

Completeness3/5

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

Two required parameters, no annotations, and no output schema mean the description is the only place to learn what comes back and under what conditions. It hints at returned links and preserved variants but leaves the return structure and the meaning of the required UUIDs implicit, which is thin for a tool whose output is undefined elsewhere.

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?

Both parameters are fully described in the schema (100% coverage), so the schema already explains that each is a "Result UUID from the corresponding discovery resource." The description adds nothing specific about the UUIDs beyond a passing reference to "Result UUID namespaces," so the baseline of 3 applies.

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

Purpose3/5

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

The description opens with a verb+resource pairing ("Get native event and category report links"), but "report links" and the tool's own use of the word "files" leave the actual payload ambiguous — an agent cannot tell whether it receives URLs, file objects, or metadata records. It offers no differentiation from plausible siblings such as motogp_standings_files, so the reader must guess which of the '*_files' tools 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool, when not to, or what alternative to prefer. The schema's "Result UUID from the corresponding discovery resource" hints at a required prerequisite, but that prerequisite is never surfaced in the description itself.

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