Skip to main content
Glama

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

TableJSON 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. 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

TableJSON 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. 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."
  2. 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"
+}
  3. First observed

TDQS

A5/5.0
Behavior5/5

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

While annotations already mark readOnlyHint=true and destructiveHint=false, the description goes far beyond by disclosing card ordering (main event first), bout and corner fields, the CORS limitation and recommendation to use proxiedImageUrl, no need for per-fighter call_api, tennis bracket truncation behavior, parallel-safety, and upstream cost. There is no contradiction with the 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 tightly organized with bolded section labels and front-loaded purpose. Every sentence either explains when to use it, what behavior to expect, or what to prefer instead. There is no filler or repetition; the density is justified by the tool's breadth across multiple games and tennis special cases.

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 tool with 7 parameters, multiple game-specific behaviors, and a tennis special path, the description is complete: it covers route selection, data shapes, alternatives, exclusions, parallel-safety, cost, and an example call. Since an output schema exists, the description appropriately focuses on decision-relevant behavior rather than restating return types.

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%, so baseline is 3, but the description adds meaningful depth to every parameter: q resolves internally, eventIdOrSlug is preferred over q, limit bounds bouts and tennis draws, drawMaxMatches fills rounds from the final backwards and reports truncation, includeMatches includes the draw, and includeStandings triggers an extra call plus rank enrichment. This goes well beyond the schema's raw descriptions.

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 a specific composite pattern ('COMPOSITE event / fight-night card: identity, bout or match list, optional standings snippet') and immediately lists concrete event types (UFC, CS2, tournament/event overview). It explicitly distinguishes itself from match_preview, match_summary, live_matches, and standings, so an agent can select it with confidence.

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 description provides explicit 'When to use', 'Prefer over', 'Prefer X for Y', and 'Do not use when' sections, naming exact sibling tools and conditions. This leaves no ambiguity about when event_card is the right tool versus alternatives like match_preview or live_matches.

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