Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

motogp_latest_session

Read-only

Read the native latest MotoGP sports-session resource and return reviewed public session, category, event and broadcast timing metadata with availability flags preserved. category_legacy_id is an optional signed numeric selector from the content-category catalog (-1, 1, 2, 3, 5, 7, 8, 9, 10, 19) and event_kind is an optional gp or test selector; omitting both preserves the source default. This is globally latest within those selectors, so a historical category can return an older session or a native 404, and returned session/category/event IDs are metadata IDs, not result UUIDs.

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 event kind, one of: gp, test. Omitting it preserves the source default.
category_legacy_idNoOptional native signed numeric category selector from the content-category catalog: -1, 1, 2, 3, 5, 7, 8, 9, 10 or 19. Omitting it preserves the source default; a historical choice can legitimately have no latest session.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Beyond readOnlyHint and openWorldHint, the description discloses that availability flags are preserved, that historical category selection can yield an older session or a native 404, and that returned session/category/event IDs are metadata IDs rather than result UUIDs. These are non-obvious failure modes and data-shape caveats that an agent would otherwise have to discover by trial.

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?

The purpose is front-loaded and the caveats are relevant, but the single dense paragraph repeats schema-level detail (both parameters are optional and default-preserving) and leans on jargon. Trimming the duplicated selector language would make the caveats more prominent.

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?

An output schema exists, so return-value explanation is unnecessary, and the description covers selectors, defaults, a plausible empty-result mode, and ID semantics. Only the lack of explicit alternative-tool guidance keeps it from being fully complete.

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 optional parameters are already documented, and the description mostly restates that they are optional selectors whose omission preserves the source default. The added nuance that the result is "globally latest within those selectors" is genuinely helpful, but the rest duplicates the schema.

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?

The description names a specific verb and resource ("Read the native latest MotoGP sports-session resource") and states what is returned (session, category, event and broadcast timing metadata with availability flags). It is distinguishable from a general listing tool like motogp_sessions by emphasizing "latest" with no explicit sibling callout, so it falls short of a 5.

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?

It explains selector behavior and warns that a historical category can return an older session or a native 404, which is useful when-to-use context. However, it never states when to prefer this over motogp_next_live_session or motogp_sessions, leaving the routing decision implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources