Skip to main content
Glama

UFCalendar Fight API — MMA MCP server

Get the record book

get_record_book
Read-onlyIdempotent

The Record Book for one promotion in one call: the top rows of every leaderboard, grouped by category — the all-time and single-night records an agent quotes. Narrow by division, country, active fighters or one scope.

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": {
      "org": "<org>"
    },
    "name": "get_record_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesPromotion slug (required — the Record Book is per promotion).
topNoRows per board. Default 3 here (the whole book at 10 rows is ~140 KB); up to 25.
scopeNoOne kind of board: career, single_fight, round, division or event. Omit for all.
countryNoISO-3166 alpha-2 nationality, e.g. "BR" — fighters from that country. Not with population=active.
divisionNoOne weight class, e.g. "lightweight", "womens-strawweight".
populationNoall (default) = everyone who fought in the promotion; active = a bout in the last ~18 months.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / division / enum
      Previous value: -[
      -  "strawweight",
      -  "flyweight",
      -  "bantamweight",
      -  "featherweight",
      -  "lightweight",
      -  "welterweight",
      -  "super-welterweight",
      -  "middleweight",
      -  "light-heavyweight",
      -  "heavyweight",
      -  "super-heavyweight",
      -  "womens-strawweight",
      -  "womens-flyweight",
      -  "womens-bantamweight",
      -  "womens-featherweight",
      -  "atomweight",
      -  "ironweight"
      -]New value: +[
      +  "strawweight",
      +  "flyweight",
      +  "bantamweight",
      +  "featherweight",
      +  "lightweight",
      +  "welterweight",
      +  "super-welterweight",
      +  "middleweight",
      +  "light-heavyweight",
      +  "cruiserweight",
      +  "heavyweight",
      +  "super-heavyweight",
      +  "womens-strawweight",
      +  "womens-flyweight",
      +  "womens-bantamweight",
      +  "womens-featherweight",
      +  "atomweight",
      +  "ironweight"
      +]
  2. Added

TDQS

A3.5/5.0
Behavior3/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 fully covered. The description adds the useful 'one promotion, one call' retrieval trait and the categorical grouping, but says nothing about board ordering, tie handling, or what happens to boards that lack data.

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?

Two dense sentences that front-load the resource and follow with narrowing options; nothing is repeated. The clause 'the all-time and single-night records an agent quotes' is slightly rhetorical but does convey the content type.

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?

There is no output schema, so the description carries responsibility for return shape, and it does describe the structure (top rows per leaderboard, grouped by category). The size/payload caveat also lives in the schema, so an agent has enough to call this correctly; only ordering semantics are absent.

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%, so the baseline is 3; the schema already explains org, top, scope, country, division and population in detail. The description adds only a light gloss — 'active fighters' maps to population=active and 'one scope' maps to the scope enum — without new syntax or precedence rules.

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 concrete payload — the top rows of every leaderboard for one promotion, grouped by category — which distinguishes it from the singular get_leaderboard sibling. It stops short of a clean verb-first statement (the action is only implied by the title), but the resource and shape are unmistakable.

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 gives narrowing advice ('Narrow by division, country, active fighters or one scope'), which is usable filtering guidance. However, it never states when to prefer this over get_leaderboard or get_rankings, nor any exclusion such as cost of calling it broadly beyond the schema's size note.

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.