Skip to main content
Glama

UFCalendar Fight API — MMA MCP server

Get a fighter's position profile

get_fighter_positions
Read-onlyIdempotent

Where one fighter's bouts happen over their career: the share of cage time at distance, in the clinch and on the ground, and seconds in control by position (back, mount, side, half guard, guard, clinch) for the fighter and against them, over their settled bouts with tracked positions. Pro plans and up.

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": {
      "fighter": "<fighter>"
    },
    "name": "get_fighter_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
fighterYesFighter slug (preferred) or numeric id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds useful behavioral context beyond annotations: data is limited to settled bouts with tracked positions, and access requires a Pro plan or higher. It does not cover error behavior or pagination, but those are secondary for this read-only retrieval tool.

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 definition is a single dense sentence that front-loads the purpose and then lists the included metrics without filler. It is somewhat long but every clause earns its place by specifying the data fields and scope.

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 one-parameter read-only retrieval tool with no output schema, the description gives enough detail about what data is included and the population restriction ('settled bouts with tracked positions'). It also notes the plan requirement. Edge cases such as fighters with no tracked positions are not addressed, which keeps it short of a 5.

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%, and the single 'fighter' parameter is fully documented in the schema as a slug or numeric id. The description adds no further parameter semantics beyond what the schema already provides, so the baseline 3 is appropriate.

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 states a specific scope: one fighter's career-level position profile, including distance, clinch, ground share and control seconds by position. The phrase 'over their career' and 'for the fighter and against them' distinguishes this career profile from fight-level siblings such as get_fight_positions.

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 implies when the tool is appropriate by describing a career position profile over settled bouts with tracked positions, and it adds a plan restriction ('Pro plans and up'). However, it does not explicitly name alternatives or say when not to use it versus related tools like get_fight_positions or get_fight_stats.

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.