Skip to main content
Glama

SportStatsAPI

Get MMA fighter

get_mma_fighter
Read-only

An MMA fighter's record (wins, losses, draws, no contests; wins and losses by KO/TKO, submission, decision) from the bouts held since 2026, with the last fights; where Wikipedia/Wikidata has the fighter also the profile (birth date, height, reach, stance, nationality, weight class, team), the career record and the fights before 2026 (cite the attribution). Or find fighters 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_mma_fighter"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNopart of a fighter's name, to find the id
fighter_idNofighter code (or number) from a bout: the record, recent fights, profile and history

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: the record, recent fights, profile and history"New value: +"fighter code (or number) from a bout: the record, recent fights, profile and history"
    • changedInput schema / properties / fighter_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / fighter_id / description
      Previous value: -"fighter id from a bout: the record and recent fights"New value: +"fighter id from a bout: the record, recent fights, profile and history"
  3. Added

TDQS

A3.6/5.0
Behavior4/5

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

Beyond readOnlyHint=true and openWorldHint=false, the description discloses meaningful behavior: the record is scoped to bouts since 2026 with pre-2026 history only where Wikipedia/Wikidata covers the fighter, and it states a citation/attribution obligation. It does not say what happens when both optional parameters are omitted or how many 'last fights' are returned, which keeps it from a 5.

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

Conciseness3/5

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

It is a single information-dense sentence with the primary payload front-loaded, so little is wasted. However, the long parenthetical enumerations make it run-on, and the trailing 'Or find fighters by name' sits awkwardly at the end rather than being structured as a separate mode.

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 carries the return-value burden and does so thoroughly, plus it flags data-source dependence on Wikipedia/Wikidata. Gaps remain on zero-argument behavior (both params optional) and on how many recent fights are included, which matters for interpretation.

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%, so both parameters are already documented in the schema, including the 'part of a name' and 'fighter code from a bout' semantics. The description confirms the name-to-id search path and that fighter_id unlocks profile and pre-2026 history, but adds no format or fallback detail beyond what the schema states.

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 the resource precisely (an MMA fighter's record) and enumerates the fields returned: wins/losses/draws/no contests, method breakdowns, recent fights, and Wikipedia/Wikidata profile fields. The sport name implicitly separates it from get_boxing_fighter, but no sibling is explicitly named or contrasted.

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?

The closing clause 'Or find fighters by name' signals the two-mode lookup (search by name to get an id, then fetch by fighter_id), which combined with the schema gives workable implied guidance. There is no explicit statement of when to prefer this over get_mma_event, get_h2h, or other siblings, and no exclusion conditions.

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