Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

by danmorris27

motogp: Get sessions

motogp_get_sessions
Read-onlyIdempotent

List all MotoGP sessions for a selected event and category by passing event and category UUIDs, then use each session ID to retrieve classification results.

Instructions

List the sessions (practice, qualifying, race, etc.) for an event and category. Pass eventUuid from motogp_get_events and categoryUuid from motogp_get_categories. Each session id feeds motogp_get_session_classification.

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

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).
event_uuidYesEvent UUID from motogp_get_events
category_uuidYesCategory UUID from motogp_get_categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds the useful pipeline detail that each session id feeds motogp_get_session_classification, but says nothing about return shape, session ordering, or rate/coverage limits beyond what annotations provide.

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?

Three short sentences, front-loaded with what the tool returns, followed by input sourcing and output routing. No filler or redundancy.

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?

There is no output schema, so the description carrying the session-id hand-off is valuable and the input chain is fully specified. It stops short of describing what a session record contains or how to use the 'fields' projection parameter, which is a minor gap for a read-only 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 description coverage is 100% and the schema already states 'Event UUID from motogp_get_events' and 'Category UUID from motogp_get_categories', so the description largely restates the schema. The optional 'fields' projection parameter is not explained in the description at all, leaving the baseline 3 appropriate.

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?

Specific verb+resource ('List the sessions') with concrete examples of session types (practice, qualifying, race) and scope narrowed to an event and category. It is clearly distinguishable from the sibling motogp_get_session_classification, which it explicitly hands off to.

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?

It states the prerequisites for the two required parameters by naming motogp_get_events and motogp_get_categories, and indicates the downstream tool that consumes the results. What's missing is any explicit 'when not to use' or alternative-tool guidance, but the chain usage is unambiguous.

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