Skip to main content
Glama

UFCalendar Fight API — MMA MCP server

by com.ufcalendar
OverviewDiscussionsAdmin

Get the UFCalendar Power Index board

get_power_index
Read-onlyIdempotent

The UFCalendar Power Index board for one promotion — our own rating engine, refreshed hourly, with peak rating and fights rated. Pass view=movers for the biggest risers over a window, view=peaks for all-time peak ratings, division= to narrow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgYesPromotion slug.
daysNoWindow for view=movers, in days. Default 365. days is snapped to 30/90/180/365/730/1825/3650.
viewNocurrent (default) = active fighters by rating; movers = biggest risers over `days`; peaks = all-time peak ratings reached in this promotion.
limitNo
divisionNoDivision slug to narrow the board, e.g. "lightweight", "light-heavyweight", "womens-strawweight".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / days
      Added value: +{
+  "description": "Window for view=movers, in days. Default 365. days is snapped to 30/90/180/365/730/1825/3650.",
+  "maximum": 3650,
+  "minimum": 30,
+  "type": "integer"
+}
    • addedInput schema / properties / division
      Added value: +{
+  "description": "Division slug to narrow the board, e.g. \"lightweight\", \"light-heavyweight\", \"womens-strawweight\".",
+  "type": "string"
+}
    • addedInput schema / properties / view
      Added value: +{
+  "description": "current (default) = active fighters by rating; movers = biggest risers over `days`; peaks = all-time peak ratings reached in this promotion.",
+  "enum": [
+    "current",
+    "movers",
+    "peaks"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A4/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 context beyond annotations: the board is 'refreshed hourly' and includes 'peak rating and fights rated.' No contradiction with annotations.

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?

Two sentences with no filler. The first sentence front-loads the core definition and the second gives actionable parameter guidance. Every clause earns its place.

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 read-only board tool with five parameters, the description covers the main usage patterns and the promotion scope. It does not explain limit behavior or return shape, but the schema covers required org, days, and view enums, and annotations cover the safety profile.

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 80%, so the schema already documents most parameters. The description adds some usage color for view and division, but it largely restates what the schema says and does not clarify the undocumented limit parameter or the days snapping behavior.

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?

The description clearly identifies the resource (UFCalendar Power Index board), the scope (one promotion), and the distinguishing nature ('our own rating engine'). It also names the view modes, making it easy to tell apart from sibling tools like get_rankings or get_leaderboard.

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 gives concrete usage guidance for view and division parameters ('Pass view=movers for the biggest risers...'), but it does not explicitly state when to use this tool versus alternatives like get_rankings or get_leaderboard. 'Our own rating engine' hints at differentiation but no exclusions or when-not-to-use guidance is provided.

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