Skip to main content
Glama

UFCalendar Fight API — MMA MCP server

by com.ufcalendar
OverviewDiscussionsAdmin

Get model win probabilities

get_predictions_upcoming
Read-onlyIdempotent

UFCalendar model win probabilities for upcoming UFC bouts, published about three weeks out and repriced at least weekly. Corner-stamped, so a probability is never shown against the wrong pair. Pass event= to narrow to one card. Informational model output, not betting advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventNoEvent slug or numeric id to narrow to one card. Omit for every upcoming UFC bout.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / event
      Added value: +{
+  "description": "Event slug or numeric id to narrow to one card. Omit for every upcoming UFC bout.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds valuable context beyond those: data is published about three weeks out and repriced at least weekly, and the corner-stamping guarantee prevents mismatched fighter/probability pairs. The betting disclaimer is also extra transparency.

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?

The description is three sentences, front-loads the core purpose, and each sentence adds distinct value: scope, freshness/repricing, correctness guarantee, parameter usage, and disclaimer. No wasted words or redundant restatements of the title.

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?

Given the simple parameter surface, the strong annotations, and the absence of an output schema, the description provides enough context for a correct invocation. It covers scope, freshness, integrity, and the optional narrowing parameter. It does not describe the exact return shape, but that is a minor gap for such a focused read-only 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 description coverage is 100%, with the event parameter already documented as an optional slug or numeric id to narrow to one card. The description repeats the same instruction ('Pass event= to narrow to one card') without adding meaning beyond the schema, so the baseline of 3 applies.

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 tool as providing UFCalendar model win probabilities specifically for upcoming UFC bouts, with additional details about publication timing and repricing. This distinguishes it from sibling tools like find_fights or get_event_card which serve different purposes.

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?

The description provides clear context: this is for upcoming UFC bouts with model predictions, and it explicitly instructs to pass event= to narrow to one card or omit for all upcoming bouts. It does not explicitly name alternatives or state when not to use it, but the context is sufficient for selection.

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