Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

motogp_standings_files

Retrieve native MotoGP standings report links by season and category UUID, preserving source report variants and UUID namespaces for accurate metadata use.

Instructions

Get native standings 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": {
      "season_uuid": "<season_uuid>",
      "category_uuid": "<category_uuid>"
    },
    "name": "motogp_standings_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
season_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.5/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it only partially delivers: "Reads anonymous native result metadata" implies a no-auth read operation, which is genuinely useful. Beyond that, "Result UUID namespaces and source report/record variants are preserved" is opaque and says nothing about return shape, link format, or limits.

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

Conciseness3/5

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

Three short sentences with no padding, so it is compact. The trade-off is that the second and third sentences are dense internal phrasing rather than front-loaded, actionable information.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description needs to explain what a caller actually receives and how links relate to source records. Instead it relies on unexplained terminology, leaving the core output ambiguous.

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%, so both UUID parameters are already documented as "Result UUID from the corresponding discovery resource." The description's mention of UUID namespaces is suggestive but adds no usable syntax or format detail beyond the schema.

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 verb+resource is present ("Get native standings report links"), so an agent knows it retrieves links rather than computed standings. However, "native" and "report links" are unexplained jargon, and the description never distinguishes this from motogp_standings or motogp_event_files, which plausibly cover overlapping ground.

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 versus motogp_standings or any other sibling, and no prerequisites beyond the schema's required UUIDs. The agent must infer selection from the tool name alone.

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