Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

motogp_sessions

Lists MotoGP event and category sessions using result UUIDs, returning anonymous results metadata with native source fields for historical categories and test events.

Instructions

List event and category sessions. Reads anonymous MotoGP results metadata using the result UUID namespace. Historical categories and test events retain their native source fields.

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

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

B3.2/5.0
Behavior3/5

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

With no annotations, the description does useful work by disclosing that this is a read of "anonymous" (no auth) results metadata and by warning that historical categories and test events expose native source fields. However, it says nothing about return shape, ordering, or what happens when the category has no sessions for that event.

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 the core action front-loaded and no filler. The closing sentence about native source fields is somewhat jargon-heavy but earns its place as a data caveat.

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?

For a two-parameter read with no annotations and no output schema, the description covers what it does and a data quirk, but leaves the agent guessing about the returned session structure and behavior for empty results. Adequate but with clear gaps.

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 description coverage is 100%, so both parameters are already documented as "Result UUID from the corresponding discovery resource." The description's "result UUID namespace" phrasing restates that without adding format, provenance, or example values, so the baseline 3 applies.

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?

"List event and category sessions" gives a specific verb plus resource and scopes it to a MotoGP event/category pair, which distinguishes it from generic session siblings like openf1_sessions. It stops short of explicitly contrasting itself with motogp_latest_session or motogp_next_live_session.

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 when-to-use or when-not-to-use guidance and no named alternative, even though siblings such as motogp_latest_session and motogp_next_live_session occupy adjacent territory. The only implied usage context comes from the two required UUID parameters, which the schema already explains.

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