Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

by danmorris27

motogp: Get events

motogp_get_events
Read-onlyIdempotent

Retrieve MotoGP Grand Prix events for a season, including circuit, country, and dates, plus each event's UUID for fetching sessions. Filter by finished events or select fields to narrow results.

Instructions

List the events (Grands Prix) in a season with circuit, country and dates. Each event's UUID feeds motogp_get_sessions.

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>"
    },
    "name": "motogp_get_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).
is_finishedNoFilter to finished events only
season_uuidYesSeason UUID from motogp_get_seasons

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so safety is covered. Beyond that, the description discloses what each event returns (circuit, country, dates) and that the returned UUID is reused by motogp_get_sessions — useful behavior not present in the annotations or schema, especially with no output schema. It does not cover pagination or whether all season events are returned.

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

Conciseness5/5

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

Two short sentences, zero filler, with the core purpose and scope front-loaded and the chaining hint placed second. Every clause earns its place.

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?

With no output schema, the description usefully summarizes the returned content and where the event UUID goes next, and all three parameters are schema-documented. The remaining gap — result count/pagination and how is_finished interacts with the listing — is minor for a simple list tool.

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%: season_uuid, fields and is_finished are each documented, including that season_uuid comes from motogp_get_seasons. The description's season scoping is consistent with the schema but adds no syntax or format detail beyond it, so baseline 3 applies.

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

Purpose5/5

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

States a specific verb (List) plus resource (events/Grands Prix) and narrows scope to a season, then names the returned fields (circuit, country, dates). The follow-on note that each event UUID feeds motogp_get_sessions cleanly separates it from siblings like motogp_get_seasons and motogp_get_sessions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The season-scoped framing tells the agent this is the step after picking a season, and the UUID-feeds-sessions sentence makes the downstream use concrete. There is no explicit when-not-to-use or alternative-tool statement, but the workflow position is clear.

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