Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

motogp_latest_session

Read MotoGP sports session metadata with optional event kind and legacy category ID; omit selectors for upstream defaults and return session, category, and event IDs.

Instructions

Read latest MotoGP sports session metadata. Reads the native sport/session resource, with optional signed legacy-category and GP/test selectors. Omission preserves the upstream default. Returned session/category/event IDs are content metadata IDs, not result-session/category UUIDs. Historical categories can return older sessions or native404. Null season fields and published timing/availability flags remain unchanged; no media or account access.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "motogp_latest_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_kindNoOptional native sports-event kind
category_legacy_idNoNative numeric legacy_id from content category catalog

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does add real context: returned IDs are content metadata IDs rather than result UUIDs, historical categories may yield older sessions or a native404, null season fields and timing/availability flags are passed through unchanged, and no media or account access is involved. It stops short of describing the response shape, which matters given there is no output schema.

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?

Purpose is front-loaded and the text is compact with no filler. However, terse jargon such as 'native404', 'signed legacy-category', and 'upstream default' compresses meaning at the cost of readability, and the caveats arrive as a dense run-on list.

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?

With no annotations and no output schema, the description must cover both safety and return behavior; it does well on safety/limits (read-only, no media or account access) and edge cases, but says nothing about what the returned session metadata contains or how an agent should interpret it.

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% and both enums are fully documented in the schema, so baseline 3 applies. The description adds only that the selectors are 'signed legacy-category and GP/test selectors' and that omission preserves upstream defaults, which is modest incremental meaning.

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 latest MotoGP sports session metadata', plus the underlying resource it reads. It does not, however, distinguish itself from the sibling 'motogp_next_live_session', so an agent must infer the boundary between 'latest' and 'next live'.

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?

Implied usage only: 'Omission preserves the upstream default' tells the agent the selectors are optional, and 'Historical categories can return older sessions or native404' warns about a narrow case. There is no explicit statement of when to pick this over motogp_sessions or motogp_next_live_session.

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