Skip to main content
Glama

UFCalendar Fight API — MMA MCP server

Get a division

get_division
Read-onlyIdempotent

One weight class in one promotion: the current rankings board when the promotion publishes one, upcoming bouts booked at that weight, the most recent results and the active roster by recency. The division-page answer in one call.

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>",
      "division": "<division>"
    },
    "name": "get_division"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesPromotion slug.
divisionYesDivision slug, e.g. "lightweight", "womens-strawweight".

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.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: rankings appear only 'when the promotion publishes one' (i.e. conditionally absent), bouts are filtered to those booked at that weight, results are the most recent, and the roster is ordered by recency.

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?

Front-loaded with the unit of data ('One weight class in one promotion') followed by a compact enumeration of contents and a one-line positioning statement. Dense but every clause carries content; only the closing 'division-page answer in one call' is slightly promotional.

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 two-parameter read tool with no output schema, the description covers what comes back, ordering, and the conditional availability of rankings. The main remaining gap is the response shape/empty-section behavior when a promotion has no rankings or no booked bouts.

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 100% with enums for both org and division, and the schema itself gives an example slug format. The description adds no parameter-level meaning, so baseline 3 applies.

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 the resource precisely: one weight class within one promotion, and enumerates the payload (rankings board, upcoming bouts, recent results, active roster). It implicitly distinguishes itself from granular siblings like get_rankings or get_event_card via 'the division-page answer in one call', but never names an alternative 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 by the phrase 'The division-page answer in one call', which suggests this is the aggregated view rather than individual lookups. There is no explicit when-to-use or when-to-prefer-a-sibling statement, and no note on prerequisites for the org/division pairing.

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.