Skip to main content
Glama

SportStatsAPI

Get boxing fighter

get_boxing_fighter
Read-only

A boxer (fighter_id): birth date, country, height, reach, stance and professional record (Wikipedia/Wikidata), world titles held now, latest bouts; or find boxers by name.

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": "get_boxing_fighter"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNopart of a boxer's name, to find the id
fighter_idNofighter code (or number) from a bout or the champions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / fighter_id / description
      Previous value: -"fighter id from a bout or the champions"New value: +"fighter code (or number) from a bout or the champions"
    • changedInput schema / properties / fighter_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare a safe read (readOnlyHint=true) and idempotentHint=false, and the description usefully discloses the data provenance (Wikipedia/Wikidata) plus freshness cues like 'world titles held now' and 'latest bouts'. It says nothing about what happens on no match, how many bouts are returned, or why the call is non-idempotent, so the added behavioral context is real but thin.

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

Conciseness4/5

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

A single dense sentence with no filler; the entity and its returned fields lead, and the name-search fallback trails where it belongs. The colon-and-list construction is compact but readable, and nothing appears redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the field enumeration is doing necessary work and covers the main payload. However, for a tool with a dual lookup mode and a non-idempotent hint, it omits resolution behavior (partial name matching, ambiguity, not-found) and any note on the volume of 'latest bouts', leaving the agent guessing on edge cases.

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 parameters are already documented in the input schema. The description adds only a light gloss — that name is a partial-match aid for finding the id and that fighter_id comes from a bout or the champions — which is marginally beyond the schema but not new semantics.

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 resource (a boxer) and enumerates the attributes returned — birth date, country, height, reach, stance, record, titles, latest bouts — plus a second mode, 'find boxers by name'. That is far more specific than a restatement of the name, and the boxing-vs-MMA framing implicitly separates it from get_mma_fighter, though no sibling is named outright.

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?

Usage is only implied: a reader infers that passing fighter_id retrieves the profile and passing name resolves an id. There is no explicit statement of when to prefer this over get_mma_fighter, get_h2h, or get_boxing_event, and no guidance for the case where both parameters are supplied or a name matches multiple boxers.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources