Skip to main content
Glama

UFCalendar Fight API — MMA MCP server

Get a bout's in-fight log

get_fight_timeline
Read-onlyIdempotent

The official in-fight log of one settled UFC bout (June 2013 onward): every logged action in order (round starts and ends, takedowns and attempts, knockdowns, submission attempts, reversals), the referee stoppages paired with their reason (eye poke, low blow, doctor check or other) and real length, and every confirmed foul of the bout. The log labels only eye pokes and low blows, so any other foul (an illegal knee to a grounded opponent, an upkick, a headbutt, a bite, a fence grab) is reported when the athletic commission's point deduction or the official result confirms it: each stoppage says whether it was a foul, which foul, which record confirms it (log, deduction or result), who committed it, the points deducted and whether the bout ended on it; a stoppage logged as "other" with no record behind it is never a foul. Stoppage reasons are logged from December 2018. A recorded foul is not a ruling on intent. Settled bouts only. Pro plans and up.

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": {
      "fight_id": "<fight_id>"
    },
    "name": "get_fight_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
fight_idYesBout id, as returned on an event card. Integer or numeric string.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: data begins June 2013, stoppage reasons only from December 2018, only eye pokes and low blows are labeled in the log, 'other' stoppages with no corroborating record are never fouls, and a recorded foul is not a ruling on intent.

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?

The core purpose is front-loaded in the opening clause, which is good, but the middle section is a dense run-on ('each stoppage says whether it was a foul, which foul, which record confirms it...') that is hard to parse in one pass. The content earns its place; the sentence structure does not.

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?

There is no output schema, so the description must describe the return shape itself, and it does — ordered action log, stoppages with reason and real length, confirmed fouls with committer, deducted points and record provenance. Coverage limits (date cutoffs, label limits) are stated, leaving nothing an agent needs in order to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With a single parameter at 100% schema coverage, the schema already defines fight_id as a bout id from an event card, integer or numeric string. The description reinforces this by scoping the whole tool to 'one settled UFC bout' and adds nothing misleading about the identifier.

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 verb-like resource: 'the official in-fight log of one settled UFC bout', then enumerates the contents (round starts/ends, takedowns, knockdowns, submission attempts, reversals, fouls). That is far more specific than the sibling names get_fight, get_fight_stats or get_fight_positions imply, though it never explicitly contrasts itself with them.

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?

It supplies eligibility constraints — 'Settled bouts only' and 'Pro plans and up' — which tell the agent when a call is valid. It gives no guidance on when to prefer this tool over the sibling stats/positions/odds lookups, so the routing decision is left to inference.

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.