Skip to main content
Glama

UFCalendar Fight API — MMA MCP server

Get a fighter's discipline record

get_fighter_discipline
Read-onlyIdempotent

The confirmed fouls in one fighter's UFC bouts since December 2018, both the ones the fighter committed and the ones committed against them: eye pokes and low blows from the official in-fight log, plus any other foul (an illegal knee to a grounded opponent, an upkick, a headbutt, a bite, a fence grab) confirmed by the athletic commission's point deduction or by the official result. Returns the counts by kind, the points deducted, the time bouts were stopped for them, fouls per 15 minutes, and every incident with the event, opponent, round and time, the foul, the record that confirms it (log, deduction or result), the points deducted and whether the bout ended on it. A stoppage with no record behind it is never counted. A recorded foul is not a ruling on intent. 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": {
      "fighter": "<fighter>"
    },
    "name": "get_fighter_discipline"
  }
}

Input Schema

NameRequiredDescriptionDefault
fighterYesFighter slug (preferred) or numeric id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior, so the bar is lower, and the description still adds real substance: the inclusion rule (only confirmed fouls), the explicit exclusion ("A stoppage with no record behind it is never counted"), the intent caveat, and the plan gating. It does not discuss latency, pagination, or behavior when a fighter has no incidents, which keeps it short of 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.

Conciseness4/5

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

The scope and both foul directions are front-loaded in the first clause, and the subsequent clauses each carry load-bearing content — return fields, inclusion rule, exclusion rule, caveat, plan requirement. It runs long for a one-parameter tool, and the parenthetical catalogue of example fouls could be trimmed, but nothing is pure padding.

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 must explain the return payload, and it does so concretely: counts by kind, points deducted, stoppage time, fouls per 15 minutes, plus per-incident event, opponent, round, time and confirming record. Together with the inclusion/exclusion rules and plan gating, an agent has everything needed to call it and interpret results.

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?

There is a single parameter with 100% schema description coverage ("Fighter slug (preferred) or numeric id"), so the schema already carries the format guidance. The description adds nothing about the fighter identifier, leaving this at the baseline for fully covered schemas.

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?

Names a specific resource (confirmed fouls in one fighter's UFC bouts) with an explicit scope boundary (since December 2018) and clarifies the two directions covered: fouls committed and fouls suffered. That framing alone separates it from siblings like get_fight_stats, get_fight_timeline or get_record_book, which would otherwise look adjacent.

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 description implies when this is the right tool by narrowing to fouls confirmed by log, commission deduction or official result, and it states an access prerequisite ("Pro plans and up"). However, it never routes the agent explicitly to or away from alternatives such as get_fight_stats or get_fight_timeline, so the user must infer the choice.

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.