Skip to main content
Glama

UFCalendar Fight API — MMA MCP server

Get a stat leaderboard

get_leaderboard
Read-onlyIdempotent

One statistical leaderboard for one promotion from UFCalendar's Record Book rollup — career, single-fight, single-round, division or event boards across 57 metrics (wins, finishes, significant strikes, takedowns, control time, finish rate and more; the 9 discipline boards on fouls and stoppages need a Pro plan), optionally narrowed to a division, a country or active fighters. Ranked, with the sample size behind each value.

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>",
      "metric": "<metric>"
    },
    "name": "get_leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesPromotion slug (required — boards are per promotion).
limitNoRows, default 25.
metricYesBoard metric, e.g. "wins", "finishes", "sig_strikes_landed", "fastest_knockout", "most_finishes_event", "finish_rate".
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. Changed1 schema field changed
    • changedInput schema / properties / metric / enum
      Previous value: -[
      -  "total_fights",
      -  "wins",
      -  "decision_wins",
      -  "title_fight_wins",
      -  "bonuses",
      -  "finishes",
      -  "win_streak",
      -  "total_fight_seconds",
      -  "avg_fight_seconds_short",
      -  "avg_fight_seconds_long",
      -  "control_time_sec",
      -  "control_time_pct",
      -  "sig_strikes_landed",
      -  "total_strikes_landed",
      -  "slpm",
      -  "sapm",
      -  "striking_differential",
      -  "sig_strike_accuracy",
      -  "sig_strike_defense",
      -  "knockdowns",
      -  "knockdowns_per_15",
      -  "knockouts",
      -  "takedowns_landed",
      -  "td_avg",
      -  "takedown_accuracy",
      -  "takedown_defense",
      -  "submission_attempts",
      -  "sub_avg_per_15",
      -  "submissions",
      -  "fastest_finish",
      -  "fastest_knockout",
      -  "fastest_submission",
      -  "longest_fight_seconds",
      -  "most_sig_strikes_fight",
      -  "most_takedowns_fight",
      -  "most_knockdowns_fight",
      -  "longest_control_fight",
      -  "most_sig_strikes_round",
      -  "most_takedowns_round",
      -  "most_knockdowns_round",
      -  "most_finishes_event",
      -  "most_knockouts_event",
      -  "shortest_card_seconds",
      -  "finish_rate",
      -  "ko_rate",
      -  "sub_rate",
      -  "decision_rate",
      -  "avg_fight_seconds"
      -]New value: +[
      +  "total_fights",
      +  "wins",
      +  "decision_wins",
      +  "title_fight_wins",
      +  "bonuses",
      +  "finishes",
      +  "win_streak",
      +  "total_fight_seconds",
      +  "avg_fight_seconds_short",
      +  "avg_fight_seconds_long",
      +  "control_time_sec",
      +  "control_time_pct",
      +  "sig_strikes_landed",
      +  "total_strikes_landed",
      +  "slpm",
      +  "sapm",
      +  "striking_differential",
      +  "sig_strike_accuracy",
      +  "sig_strike_defense",
      +  "knockdowns",
      +  "knockdowns_per_15",
      +  "knockouts",
      +  "takedowns_landed",
      +  "td_avg",
      +  "takedown_accuracy",
      +  "takedown_defense",
      +  "submission_attempts",
      +  "sub_avg_per_15",
      +  "submissions",
      +  "fastest_finish",
      +  "fastest_knockout",
      +  "fastest_submission",
      +  "longest_fight_seconds",
      +  "most_sig_strikes_fight",
      +  "most_takedowns_fight",
      +  "most_knockdowns_fight",
      +  "longest_control_fight",
      +  "most_sig_strikes_round",
      +  "most_takedowns_round",
      +  "most_knockdowns_round",
      +  "fouls_committed",
      +  "eye_pokes_committed",
      +  "low_blows_committed",
      +  "fouls_drawn",
      +  "fouls_per_15",
      +  "most_fouls_fight",
      +  "longest_foul_stoppage_fight",
      +  "most_fouls_event",
      +  "most_finishes_event",
      +  "most_knockouts_event",
      +  "shortest_card_seconds",
      +  "finish_rate",
      +  "ko_rate",
      +  "sub_rate",
      +  "decision_rate",
      +  "avg_fight_seconds",
      +  "fouls_per_15_division"
      +]
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish this is a safe, idempotent read, so the description adds real value on top: it discloses a plan-gating rule (Pro required for discipline boards), that exactly one board is returned per call, and that results are ranked with the sample size behind each value. It does not describe error behavior for metrics unavailable in a promotion, but the gating and output shape are meaningful additions beyond the annotations.

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 purpose is front-loaded and the parenthetical detail about board families, metric count, and the Pro-plan caveat is compactly packed into a single sentence plus a short trailing fragment. It is dense but not padded; each clause carries information an agent would otherwise have to probe for.

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?

With no output schema, the description carries the burden of describing return values and does so — ranked rows with sample sizes. It also covers the plan constraint and the narrowing options. The remaining gap is the absence of any offset/pagination note for the 100-row limit, which is a minor omission for a read-only list tool.

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 all six parameters including the org and metric enums are already documented, which sets the baseline at 3. The description adds a small amount — grouping the metrics into career/single-fight/single-round/division/event families and noting the division, country, and active-fighter narrowing — but nothing about limit behavior or the country-vs-active exclusion beyond what the schema already states.

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?

States a specific verb and resource ('One statistical leaderboard for one promotion') and defines scope: one board per call, drawn from the Record Book rollup. The clause listing board families (career, single-fight, single-round, division, event) plus 57 metrics tells an agent exactly what kind of data comes back, though it never names a sibling such as get_record_book or get_rankings to differentiate itself explicitly.

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?

Usage is only implied: the description makes clear this returns one metric's ranked list, so an agent can infer it is the wrong tool for multi-metric summaries, but no alternative is named and no when-not-to-use condition is stated. The one real constraint it surfaces — the 9 discipline boards on fouls and stoppages require a Pro plan — is a useful caveat rather than routing guidance.

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.