Cito API

event_card

Read-only

COMPOSITE event / fight-night card: identity, bout or match list, optional standings snippet.

When to use:

UFC fight night / numbered event page ("UFC 300 card", "Fight Night")
CS2 event hub with match list
Tournament/event overview before match_preview drill-down

Bouts come back in card order — main event first, then prelims, then early prelims. Each bout carries weightClass, titleBout, card placement, and (once fought) result { method, round, time, referee, winnerSlug }. Each corner carries images { headshotUrl, bodyImageUrl, imageUrl, proxiedImageUrl }, record, nickname, rank, championStatus, country and flag when upstream supplies them. Use proxiedImageUrl in browsers — ufc.com sends no CORS header. You do not need call_api per fighter for faces.

Prefer over: agent-side resolve + call_api /ufc/events + bout expansion; N+1 match_summary for the card list only; per-fighter call_api just to fetch headshots.

Prefer match_preview for one bout/match briefing; match_summary for completed recaps; live_matches for live-only strips; standings alone for pure tables.

Do not use when: you only need live scores (live_matches); single finished match recap (match_summary); no event name/id yet and game unknown.

Tennis: pass a tournament id/slug to get the draw bracket — rounds carry a round code (Q1..R128, QF, SF, F) with each match's players and score. Set is the primary tennis path here; there is no separate draw tool.

Parallel-safe: yes. Upstream cost: 1–4. Example: { "game": "ufc", "eventIdOrSlug": "ufc-300", "includeMatches": true, "includeStandings": false }

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Free-text event name when id/slug unknown. Example: "UFC 300". Resolves within this tool — still prefer resolve_entity when disambiguating many hits.
`game`	Yes	Game title: lol \| cs2 \| dota2 \| cod \| ufc \| tennis. Example: "cs2".
`limit`	No	Max bouts/matches on the card (default 20, max 50).
`eventIdOrSlug`	No	Event or tournament id/slug. Prefer over q when known. Required unless q is given. Example: "ufc-300".
`includeMatches`	No	Include the bout/match list, or the tennis draw bracket (default true).
`includeStandings`	No	Include standings/rankings snippet when API supports event/tournament/division scope (default false). For UFC this also joins divisional rank and movement onto each bout corner as team.rank / team.rankMovement — bout rows themselves carry no rank. Costs one extra upstream call.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	true if the tool succeeded
`data`	No	Result payload when ok is true; null on error
`meta`	Yes
`error`	No
`partial`	No
`pagination`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedSep 5, 2026

removedInput schema / properties / includeBouts

Removed value: -{
-  "default": true,
-  "description": "Include bout/match list (default true).",
-  "type": "boolean"
-}

addedInput schema / properties / includeMatches

Added value: +{
+  "default": true,
+  "description": "Include the bout/match list, or the tennis draw bracket (default true).",
+  "type": "boolean"
+}

First observedSep 1, 2026

TDQS

A5/5.0

Behavior5/5

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

The annotations only declare readOnly, openWorld, and destructive-safe, so the description carries the behavioral burden. It adds card ordering, bout/corner field details, the CORS/proxiedImageUrl caveat, parallel-safety, upstream cost, the extra includeStandings call, and tennis draw behavior—far beyond the structured 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?

The description is long but every section earns its place: definition, use cases, return behavior, CORS warning, alternative routing, exclusions, tennis path, and a concrete example. It is front-loaded with the core identity and organized so an agent can scan it efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a composite, multi-game tool with six parameters and many siblings, the description is complete: it covers selection criteria, alternative tools, exclusions, field semantics, cost, safety, parallel execution, and special tennis behavior. Since an output schema exists, return-value documentation is not required here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds meaningful behavior beyond it: q resolves within the tool and should defer to resolve_entity for disambiguation; includeMatches includes the tennis draw bracket; includeStandings joins divisional rank onto corners and costs an extra upstream call. These are the kind of side effects an agent cannot infer from the schema alone.

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 opens with 'COMPOSITE event / fight-night card: identity, bout or match list, optional standings snippet,' which clearly names the resource and scope. It also distinguishes itself from siblings by pointing to match_preview for one bout, match_summary for recaps, live_matches for live-only, and standings for pure tables.

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

Usage Guidelines5/5

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

The 'When to use' section lists concrete scenarios, including UFC fight nights, CS2 event hubs, and tournament overviews. 'Prefer over' and 'Do not use when' explicitly route the agent to alternatives and state exclusion conditions, and the tennis guidance adds platform-specific handling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Cito API tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool has a clearly distinct job, and the descriptions explicitly separate temporal states (live vs upcoming vs preview vs recap vs deep-dive) and interaction modes (one-best resolve vs browse search, curated tool vs raw escape hatch). Even the match/event families are carefully tiered so an agent should rarely misselect.

Naming Consistency3/5

Names are readable and grouped into recognizable families like list_*, match_*, and *_profile, but the overall convention is mixed: verb-prefixed names like resolve_entity and call_api sit alongside noun-phrase names like event_card, match_summary, and standings. Consistent snake_case prevents chaos, but there is no uniform verb_noun pattern.

Tool Count4/5

16 tools is at the upper edge of the ideal range, but the server spans multiple games and several composite read workflows, so each tool has a distinct purpose. It feels slightly heavy but not bloated.

Completeness4/5

The set covers health, discovery, entity resolution, profiles, standings, schedules, live matches, previews, recaps, and deep-dive match data, with call_api as an escape hatch for long-tail routes. Notable omissions like a standalone historical results search and some per-game upstream gaps keep it from a perfect score.

Resources

Need Help?