Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

by danmorris27

motogp: Get riders

motogp_get_riders
Read-onlyIdempotent

List MotoGP riders with profile details such as name, number, country, and team, and filter by category UUID when needed.

Instructions

List MotoGP riders with their profile data (name, number, country, team). Optionally filter by category UUID.

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

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).
category_uuidNoCategory UUID to filter riders (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

B3.4/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 fully covered and the description need not restate it. The description adds only the set of profile fields returned, with no note on pagination, result size, or what an empty/no-match result looks like.

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 tight sentences: the resource and returned fields are front-loaded, and the optional filter follows. 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?

For a simple read-only listing tool with full annotation coverage and a fully documented schema, the description is sufficient. The absence of any return-shape or pagination note is a minor gap given no output schema exists.

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 the schema already documents both fields and category_uuid; baseline is 3. The description restates the category UUID filter but does not clarify the 'fields' projection parameter or give UUID format examples.

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?

Clear verb (List) plus resource (MotoGP riders) and the returned profile fields (name, number, country, team). It is distinguishable from f1_get_drivers and openf1_get_drivers via the MotoGP scope, but it never differentiates itself from its own sibling motogp_get_standings, 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 Guidelines2/5

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

The only guidance is 'Optionally filter by category UUID,' which is a parameter note rather than a when-to-use rule. There is no mention of when to prefer this over motogp_get_standings, motogp_get_categories, or other rider/driver listing tools.

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