Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

motogp: Get categories

motogp_get_categories
Read-onlyIdempotent

List MotoGP, Moto2, Moto3, and MotoE racing categories for a season and return their UUIDs. Use a season UUID to retrieve category UUIDs for sessions and standings.

Instructions

List the racing categories (MotoGP, Moto2, Moto3, MotoE) for a season, with their UUIDs. Use a seasonUuid from motogp_get_seasons; the returned categoryUuid feeds sessions and standings.

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

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).
season_uuidYesSeason UUID from motogp_get_seasons

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / fields
      Added value: +{
      +  "description": "Keys to keep (comma-separated).",
      +  "type": "string"
      +}
  2. Addedv1.3.0

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 useful output context (categories plus their UUIDs) but says nothing about rate limits, result size, or ordering beyond what the 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?

Two sentences, zero waste: the first delivers purpose and return shape, the second delivers the input source and downstream destination. Information is front-loaded and 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 correctly carries the return-value burden by naming the categories and their UUIDs, and it documents the upstream/downstream data flow. The only gap is the semantics of the optional 'fields' projection parameter, which is left to the schema.

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 season_uuid description already states 'Season UUID from motogp_get_seasons', so the description mostly repeats structured data. It adds no detail on the 'fields' key-filtering syntax beyond what the schema supplies. Baseline 3 is appropriate when the schema carries the parameter burden.

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 and resource ('List the racing categories ... for a season'), enumerates the exact values returned (MotoGP, Moto2, Moto3, MotoE), and notes the UUIDs included. It positions the tool within the MotoGP family by naming motogp_get_seasons as the source of the input, so an agent can distinguish it from siblings without opening the schema.

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?

Explicitly says to obtain the seasonUuid from motogp_get_seasons and that the returned categoryUuid feeds sessions and standings, which gives clear workflow placement. It stops short of stating when NOT to use it or naming a direct alternative, but no sibling offers equivalent category listing, so the guidance is effectively complete.

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