Skip to main content
Glama
Sign In

Cito API

by com.citoapi.api
OverviewDiscussionsAdmin

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 — the image host 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

NameRequiredDescriptionDefault
qNoFree-text event name when id/slug unknown. Example: "UFC 300". Resolves within this tool — still prefer resolve_entity when disambiguating many hits.
gameYesGame title: lol | cs2 | dota2 | cod | ufc | tennis | valorant. Example: "cs2".
limitNoMax bouts/matches on the card (default 20, max 50). For a tennis draw this bounds the flat `bouts` list; the bracket in `draw.rounds` is returned whole by default, because a truncated bracket is not a bracket. Use drawMaxMatches to bound it.
eventIdOrSlugNoEvent or tournament id/slug. Prefer over q when known. Required unless q is given. Example: "ufc-300".
drawMaxMatchesNoTennis only. Cap the total matches carried in draw.rounds. The round list is filled from the business end backwards (Final, SF, QF, …) so a small cap keeps the decisive rounds and drops the early ones; draw.truncated and draw.omitted report what happened. Omit for the complete bracket.
includeMatchesNoInclude the bout/match list, or the tennis draw bracket (default true).
includeStandingsNoInclude 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

NameRequiredDescriptionDefault
okYestrue if the tool succeeded
dataNoResult payload when ok is true; null on error
metaYes
errorNo
partialNo
paginationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / game / description
      Previous value: -"Game title: lol | cs2 | dota2 | cod | ufc | tennis. Example: \"cs2\"."New value: +"Game title: lol | cs2 | dota2 | cod | ufc | tennis | valorant. Example: \"cs2\"."
    • changedInput schema / properties / game / enum
      Previous value: -[
-  "lol",
-  "cs2",
-  "dota2",
-  "cod",
-  "ufc",
-  "tennis"
-]New value: +[
+  "lol",
+  "cs2",
+  "dota2",
+  "cod",
+  "ufc",
+  "tennis",
+  "valorant"
+]
    • changedInput schema / properties / includeStandings / description
      Previous value: -"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 API call."New value: +"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."
  2. Changed1 schema field changed
    • changedInput schema / properties / includeStandings / description
      Previous value: -"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."New value: +"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 API call."
  3. Changed2 schema fields changed
    • addedInput schema / properties / drawMaxMatches
      Added value: +{
+  "description": "Tennis only. Cap the total matches carried in draw.rounds. The round list is filled from the business end backwards (Final, SF, QF, …) so a small cap keeps the decisive rounds and drops the early ones; draw.truncated and draw.omitted report what happened. Omit for the complete bracket.",
+  "maximum": 500,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Max bouts/matches on the card (default 20, max 50)."New value: +"Max bouts/matches on the card (default 20, max 50). For a tennis draw this bounds the flat `bouts` list; the bracket in `draw.rounds` is returned whole by default, because a truncated bracket is not a bracket. Use drawMaxMatches to bound it."
  4. Changed2 schema fields changed
    • 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"
+}
  5. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), yet the description adds real operational context: card ordering (main event first, then prelims), per-bout and per-corner payload fields, the CORS caveat on proxiedImageUrl, parallel-safety, and an explicit upstream cost of 1–4 calls. It omits only failure/empty-result behavior and truncation edge cases beyond tennis, so it falls short of a 5.

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-loads the composite identity, then usage, routing, payload shape and example — a sensible priority order with no filler sentences. It is on the long side and the 'Prefer over' and 'Prefer' lists restate routing rules, mildly redundant but not bloated.

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?

A 7-parameter tool with a rich schema and an output schema, and the description still covers when to call, what comes back, the tennis draw path, per-parameter tradeoffs and cost. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema alone does not foreground: a worked example call, the includeStandings extra-call cost, and the reason limit and drawMaxMatches split (a truncated bracket is not a bracket). That is above-baseline value, though it largely echoes the schema's own field explanations.

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?

"COMPOSITE event / fight-night card: identity, bout or match list, optional standings snippet" names the resource and its returned parts specifically, and the same paragraph distinguishes it from match_preview, match_summary, live_matches and standings. An agent can identify the tool without opening the schema.

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?

Explicit when-to-use bullets (UFC card, CS2 event hub, tournament overview before drill-down), a 'Prefer over' list naming concrete alternative approaches, and a 'Do not use when' clause with three exclusions. Routing is fully determined.

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

All Cito API 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