Skip to main content
Glama
Sign In

Cito API

by com.citoapi.api
OverviewDiscussionsAdmin

standings

Read-only

League/event standings or world/division rankings normalized to ranked rows.

When to use:

  • Table / playoff picture

  • UFC rankings; CS2 world or event standings; CDL standings; LoL league/tournament tables

Prefer over: raw standings via call_api for agent-normalized rows.

Do not use when: single team form → team_profile; live scores → live_matches. Dota has no first-class standings (may NOT_IMPLEMENTED or weak worldRanking).

Required scope keys by game:

  • lol: leagueId OR tournamentId

  • cs2: omit for world rankings; eventId for event standings

  • cod: optional season/stage

  • ufc: optional division (scope=division)

  • tennis: optional division (ATP or WTA tour; default ATP)

  • dota2: best-effort worldRanking only

Parallel-safe: yes. Upstream cost: 1–2. Example: { "game": "cod", "season": "2026", "limit": 50 }

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": {
      "game": "<game>"
    },
    "name": "standings"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameYesGame title: lol | cs2 | dota2 | cod | ufc | tennis | valorant. Example: "cs2".
pageNoTennis only: page over the full published ranking list. With limit=5 the ATP list is 30 pages (150 ranked players); the response reports total/rankedPlayers/totalPages/hasMore.
limitNoMax items to return (default 50, max 100). Example: 50.
scopeNoInterpretation depends on game; defaults sensibly per game.
stageNoStage key (COD / LoL).
cursorNoOpaque cursor from pagination.nextCursor. UFC world scope spans every division; page with it rather than raising limit.
regionNoValorant ranking region (europe, north-america, brazil, asia-pacific, korea, japan, china, mena, oceania, la-s, la-n, gc). Default europe.
seasonNoSeason key (COD).
eventIdNoCS2 event id for event standings.
divisionNoUFC division key.
leagueIdNoLoL league id for league standings.
tournamentIdNoLoL/COD tournament id.

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. Changed4 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"
+]
    • addedInput schema / properties / region
      Added value: +{
+  "description": "Valorant ranking region (europe, north-america, brazil, asia-pacific, korea, japan, china, mena, oceania, la-s, la-n, gc). Default europe.",
+  "examples": [
+    "europe"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / season / description
      Previous value: -"Season key (COD). Tennis: a year (YYYY) gives that season's last published ranking list."New value: +"Season key (COD)."
  2. Changed1 schema field changed
    • changedInput schema / properties / season / description
      Previous value: -"Season key (COD)."New value: +"Season key (COD). Tennis: a year (YYYY) gives that season's last published ranking list."
  3. Changed1 schema field changed
    • addedInput schema / properties / page
      Added value: +{
+  "description": "Tennis only: page over the full published ranking list. With limit=5 the ATP list is 30 pages (150 ranked players); the response reports total/rankedPlayers/totalPages/hasMore.",
+  "minimum": 1,
+  "type": "integer"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Opaque cursor from pagination.nextCursor. UFC world scope spans every division; page with it rather than raising limit.",
+  "type": "string"
+}
  5. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses that calls are parallel-safe, the upstream cost (1–2), and a real failure mode: Dota2 has no first-class standings and may return NOT_IMPLEMENTED or a weak worldRanking. That error-condition disclosure is exactly the kind of context the annotations cannot carry.

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?

Hard front-loaded purpose sentence followed by labeled sections (When to use / Prefer over / Do not use when / scope keys / cost / example). Every line carries operational information; no restatement of the name or schema boilerplate.

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 12-parameter, multi-game tool this is close to complete: per-game scope requirements, pagination hints, cost, concurrency safety, and a degraded-mode warning are all present, and an output schema exists so return-value detail is legitimately omitted. The only minor hole is the unlisted valorant scope requirement, which the region parameter partially compensates for.

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 already 100%, yet the description adds genuine meaning by mapping which scope keys each game requires (lol needs leagueId or tournamentId, cs2 uses eventId only for event standings, tennis division defaults to ATP). The gap: 'valorant' is in the game enum and has a region parameter, but the required-scope table omits it, leaving that branch ambiguous.

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 verb-and-resource statement ('League/event standings or world/division rankings normalized to ranked rows') that tells an agent exactly what comes back, not just what is fetched. It also names the siblings it is not (team_profile, live_matches, call_api), so the tool is distinguishable 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 Guidelines5/5

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

It gives explicit when-to-use bullets ('Table / playoff picture', 'UFC rankings', 'CS2 world or event standings'), an explicit prefer-over rule against raw call_api, and an explicit do-not-use section routing single-team form and live scores to named alternatives. Both sides of the selection decision are covered.

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