Skip to main content
Glama

UFCalendar Fight API — MMA MCP server

Get a bout's position stats

get_fight_positions
Read-onlyIdempotent

Where one settled UFC bout was fought and who held control (tracked reliably from 2007): seconds standing, at distance, in the clinch and on the ground, each fighter's control time by position (clinch, back, mount, side, half guard, guard), and strikes landed and attempted by position and target, for the whole bout and per round. null means not tracked for that bout, 0 is a real zero. 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_positions"
  }
}

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

A4.1/5.0
Behavior5/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world call, and the description still adds meaningful behavior the annotations cannot: reliable tracking from 2007, the null-vs-zero convention ("null means not tracked for that bout, 0 is a real zero"), and the settlement/paywall gate. These are exactly the caveats an agent needs to interpret results and avoid mis-reporting zeros.

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 core purpose, followed by a dense but purposeful enumeration and two short caveat sentences. The long list of positions is informative rather than padded, though it could be tightened slightly.

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?

With no output schema, the description carries the burden of describing returns and does so thoroughly: positional breakdown, per-round granularity, null semantics, coverage start year, and access tier. An agent has enough to call it and interpret the payload 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% and the single fight_id is documented with type and format, so the schema does the work. The description's mention of "one settled UFC bout" reinforces but does not extend the parameter's meaning. Baseline 3 applies.

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 opens with a specific verb and resource — where a single settled UFC bout was fought and who held control — then enumerates exactly what is returned (positional seconds, control time by position, strikes by position/target). That makes it clearly narrower than get_fight_stats or get_fighter_positions, though it never names those siblings explicitly.

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?

"Settled bouts only. Pro plans and up." gives concrete eligibility constraints (no upcoming/unsettled bouts, paid tier required), which is real when-to-use context. It stops short of routing the agent to an alternative such as get_fight_stats or get_fighter_positions when bout-level rather than positional data is wanted.

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.