Skip to main content
Glama

Fight

get_fight
Read-onlyIdempotent

Use for everything about one fight: the result, both fighters' full stat sheets (strikes by target and position, takedowns, control time, guard passes, reversals, submission attempts; UFC only, null elsewhere and where the source has no sheet), round-by-round lines (UFC only), each fighter's rating before and after, and the opening and closing moneyline from each book that posted one (2024 on). 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": {
      "bout_id": "<bout_id>"
    },
    "name": "get_fight"
  }
}

Input Schema

NameRequiredDescriptionDefault
leagueNoLeague. Defaults to mma. One of: mma, pfl, bellator.
bout_idYesFight id (bout_id) from get_event or get_fighter_fights.

Output Schema

NameRequiredDescriptionDefault
boutYes
oddsYes
roundsYes
fightersYes
rounds_noteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the description adds genuinely new behavior: a 5-credit cost, the explicit null convention for non-UFC leagues and missing source sheets, the '2024 on' coverage window for moneylines, and the no-wagering disclaimer. Only pagination/response-size behavior is left unstated.

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?

The guidance sentence is front-loaded, followed by one dense but scannable enumeration and two short qualifiers on cost and wagering. The long parenthetical is justified because it tells the agent precisely which fields are and are not populated.

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 an output schema present, return values did not need spelling out, yet the description still covers them, leaving nothing essential unclear for calling the tool. It is complete, though the field enumeration partially duplicates the output schema rather than covering gaps such as response size.

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%, and both the bout_id provenance (get_event/get_fighter_fights) and the league enum with its mma default are already documented in the schema itself. The description adds only indirect semantics, noting some fields are UFC-only, which hints at the league parameter's effect but does not elaborate on it.

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?

The description opens with a specific verb+resource+scope: 'Use for everything about one fight', then enumerates exactly what the record contains (result, stat sheets, round lines, ratings, moneylines). This lets an agent distinguish it from get_event, get_fighter and get_odds without opening any 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?

'Use for everything about one fight' gives clear selection context and implies it supersedes the narrower siblings for a single bout. It stops short of naming when NOT to use it or pointing to alternatives (e.g. get_line_movement for odds history), so it is clear but not fully routing.

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.