Skip to main content
Glama

Fighter fights

get_fighter_fights
Read-onlyIdempotent

Use for a fighter's full history in the promotion: every fight with the opponent, result, method, round, time, strikes landed and absorbed and takedowns (UFC only), rating before and after, and the median closing moneyline across sportsbooks. Costs 5 credits. Prices are market information; no tool places, accepts or tracks wagers.

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": {
      "fighter_id": "<fighter_id>"
    },
    "name": "get_fighter_fights"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax fights (default 50).
leagueNoLeague. Defaults to mma. One of: mma, pfl, bellator.
offsetNoPage offset; use next_offset.
fighter_idYesFighter id from search_fighters.

Output Schema

NameRequiredDescriptionDefault
countYes
fightsYes
fighter_idYes
next_offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts: a 5-credit cost, a UFC-only caveat on the strike/takedown fields, and an explicit statement that prices are market information with no wagering capability — which usefully clarifies what the odds data is and is not.

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?

Front-loaded with the use case and the return payload, followed by two short, purposeful sentences on cost and on the market-information disclaimer. The field enumeration is long but each item carries selection value; nothing is redundant.

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

Completeness5/5

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

For a read-only, paginated lookup with an output schema, full parameter documentation and rich annotations, the description covers the remaining unknowns: cost, coverage caveats, and the nature of the odds data. An agent has everything needed to decide and to call it correctly.

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 limit, offset, league and fighter_id are already documented, which sets the baseline at 3. The '(UFC only)' note does add real meaning by implying that the league parameter affects which fields are populated, but limit/offset paging semantics are left entirely to the schema.

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 states a specific resource and scope: 'a fighter's full history in the promotion,' then enumerates exactly what comes back (opponent, result, method, round, time, strikes, takedowns, ratings, moneylines). That makes it clearly distinguishable in substance from a single-fight or fighter-profile tool. It stops short of naming a sibling to contrast against, so it lands at 4 rather than 5.

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?

'Use for a fighter's full history' establishes the intended use case, but there is no when-not guidance and no named alternative (e.g., when a profile lookup or a single fight lookup is the better call). The reader must infer the boundary from sibling names alone.

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.