Skip to main content
Glama

UFCalendar Fight API — MMA MCP server

by com.ufcalendar
OverviewDiscussionsAdmin

Get a bout

get_fight
Read-onlyIdempotent

Fetch one bout by id. Pass include=stats for per-fight totals, include=rounds for round-by-round statistics, include=scorecards for the official judges’ cards, include=odds for the current UFCalendar consensus odds line (the closing line once the bout is settled) (information only, not betting advice).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeNoExtra blocks to fetch in the same call. odds = the latest UFCalendar consensus line (information only, not betting advice).
fight_idYesBout id, as returned on an event card. Integer or numeric string.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / include / description
      Previous value: -"Extra blocks to fetch in the same call."New value: +"Extra blocks to fetch in the same call. odds = the latest UFCalendar consensus line (information only, not betting advice)."
    • changedInput schema / properties / include / items / enum
      Previous value: -[
-  "stats",
-  "rounds",
-  "scorecards"
-]New value: +[
+  "stats",
+  "rounds",
+  "scorecards",
+  "odds"
+]
  2. Changed3 schema fields changed
    • addedInput schema / properties / fight_id / anyOf
      Added value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^\\d+$",
+    "type": "string"
+  }
+]
    • changedInput schema / properties / fight_id / description
      Previous value: -"Numeric bout id, as returned on an event card."New value: +"Bout id, as returned on an event card. Integer or numeric string."
    • removedInput schema / properties / fight_id / type
      Removed value: -"string"
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral detail beyond the schema, such as the odds being the UFCalendar consensus line and the closing line once settled, plus an information-only disclaimer.

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?

Single sentence, front-loaded with the core verb and resource, then a compact enumeration of optional includes. Every phrase earns its place, including the parenthetical odds clarification, with no filler or repetition.

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?

For a simple by-id fetch with one required parameter and optional include blocks, the description covers what the tool returns and the meaning of each include. It does not describe error behavior or explicitly mention that multiple includes can be combined, but the schema already communicates the parameter structure.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning by explaining what each include value returns: stats as per-fight totals, rounds as round-by-round statistics, scorecards as official judges' cards, and odds as the consensus line. This goes beyond the enum names in the schema.

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?

Description states a precise action: 'Fetch one bout by id,' identifying both the resource (bout/fight) and the lookup mechanism. This clearly distinguishes it from sibling search tools like find_fights and from event-level tools like get_event_card.

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?

The description makes it clear this is the tool to use when you already have a bout id and want the bout record plus optional related blocks. It does not explicitly exclude alternatives such as find_fights or get_fight_odds, but the by-id framing gives sufficient contextual guidance for a simple retrieval tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All UFCalendar Fight API — MMA MCP server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources