Cito API

head_to_head

Read-only

Composed head-to-head record between two teams, two UFC fighters, or two tennis players. No first-class REST H2H exists — this tool filters match history server-side.

When to use:

Rivalry / series record questions
Supporting context for previews

Prefer over: agent-side double match-list filtering.

Do not use when: single-side form only → team_profile or player_profile.

Caveat: Dota filters are weaker; expect meta.warnings when data is sparse.

Parallel-safe: yes. Upstream cost: 2–4. Example: { "game": "cs2", "sideA": "faze", "sideB": "navi", "limit": 20 }

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>",
      "sideA": "<sideA>",
      "sideB": "<sideB>"
    },
    "name": "head_to_head"
  }
}

Input Schema

Name	Required	Description	Default
`to`	No	ISO-8601 upper bound on meeting startTime (client filter).
`from`	No	ISO-8601 lower bound on meeting startTime (client filter).
`game`	Yes	Game title: lol \| cs2 \| dota2 \| cod \| ufc \| tennis \| valorant. Example: "cs2".
`limit`	No	Max meetings returned.
`sideA`	Yes	Id or slug for side A.
`sideB`	Yes	Id or slug for side B.
`entityType`	No	team (default), fighter (UFC), or player (tennis).	team

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

Changed5 schema fields changedNov 14, 2026

removedInput schema / properties / bestOf

Removed value: -{
-  "description": "CS2 only: series length, 1, 3 or 5, or a comma list (\"3,5\"). \"3\" returns BO3 matches only (filtered by the API, so paging stays right).",
-  "examples": [
-    "3"
-  ],
-  "type": "string"
-}

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 / sideA / description

Previous value: -"Id or slug for side A (tennis: atp_207989 or a player name)."New value: +"Id or slug for side A."

changedInput schema / properties / sideB / description

Previous value: -"Id or slug for side B (tennis: atp_206173 or a player name)."New value: +"Id or slug for side B."

Changed1 schema field changedNov 11, 2026

addedInput schema / properties / bestOf

Added value: +{
+  "description": "CS2 only: series length, 1, 3 or 5, or a comma list (\"3,5\"). \"3\" returns BO3 matches only (filtered by the API, so paging stays right).",
+  "examples": [
+    "3"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedNov 5, 2026

changedInput schema / properties / sideA / description

Previous value: -"Id or slug for side A."New value: +"Id or slug for side A (tennis: atp_207989 or a player name)."

changedInput schema / properties / sideB / description

Previous value: -"Id or slug for side B."New value: +"Id or slug for side B (tennis: atp_206173 or a player name)."

First observedSep 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare read-only, non-destructive, open-world behavior, yet the description still adds real value: the server-side filtering mechanism, a data-quality caveat ('Dota filters are weaker; expect meta.warnings when data is sparse'), and operational traits ('Parallel-safe: yes. Upstream cost: 2–4'). The only minor gap is that it doesn't say how the composed record is shaped on failure or when no meetings exist, though the output schema offsets that.

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?

Front-loaded one-sentence purpose followed by short labeled blocks (When to use / Prefer over / Do not use when / Caveat / Parallel-safe / Example) — scannable and each block carries distinct information. No sentence restates the title or the schema.

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?

With an output schema present, return values need not be explained, and the description covers routing, caveats, cost, and concurrency for a 7-parameter tool. The one omission is that the sibling h2h_matrix is never addressed, leaving an agent unsure how this differs from a matrix-style H2H 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 coverage is 100%, so game, sideA/sideB, entityType, from/to, and limit are all documented in structured form. The description adds only a worked example ('game: cs2, sideA: faze, sideB: navi, limit: 20') and the 'Id or slug' acceptance hint, without clarifying edge cases like how entityType interacts with the game enum (e.g. ufc→fighter, tennis→player). Baseline 3.

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?

States a specific verb and resource — 'Composed head-to-head record between two teams, two UFC fighters, or two tennis players' — and explains the mechanism ('filters match history server-side') because no REST H2H endpoint exists. An agent can immediately tell what it returns and how, and the entity coverage (team/fighter/player) further disambiguates it.

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?

Explicitly enumerates when to use ('rivalry / series record questions', 'previews'), names the alternative it replaces ('agent-side double match-list filtering'), and gives a negative case with concrete sibling routing ('single-side form only → team_profile or player_profile'). This is the full when/when-not/alternatives triad.

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

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

Need Help?