Skip to main content
Glama
Sign In

UFCalendar Fight API — MMA MCP server

by com.ufcalendar
OverviewDiscussionsAdmin

Get a referee

get_referee
Read-onlyIdempotent

One referee's career aggregates by slug (e.g. herb-dean): bouts worked per promotion, first and last bout, finish rate, method breakdown and average fight time. Same shape as a list_referees row; use get_referee_fights for the bouts themselves.

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": {
      "referee": "<referee>"
    },
    "name": "get_referee"
  }
}

Input Schema

NameRequiredDescriptionDefault
refereeYesReferee slug from list_referees, e.g. "herb-dean". A name spelled the same way works too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already carry the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the return structure — aggregates only, mirroring a list_referees row — which is genuinely useful given there is no output schema. It omits lookup-failure behavior for a bad slug, which is the main remaining gap.

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, no padding: the first front-loads what is returned, the second gives sibling routing. 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?

With no output schema, the description compensates well by listing the aggregate fields and tying the response shape to list_referees. Only missing piece is error/empty handling for an unrecognized slug on a high-cardinality key.

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 schema already documents the slug with the same 'herb-dean' example; the description's 'by slug (e.g. herb-dean)' is largely redundant. Baseline 3 is appropriate when the schema does all the parameter work.

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?

States a specific verb and resource ('one referee's career aggregates by slug') and enumerates exactly what is returned: bouts per promotion, first/last bout, finish rate, method breakdown, average fight time. It also names the sibling it is not (list_referees for rows, get_referee_fights for bouts), so an agent can distinguish it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the bouts-themselves use case to get_referee_fights and clarifies the relationship to list_referees ('same shape as a list_referees row'). It does not state prerequisites or when-not conditions (e.g. unknown slug behavior), so it stops short of full guidance.

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