Cito API

team_profile

Read-only

Team/org card: identity, roster, recent matches, and form/trends/radar when available.

When to use:

Team page / "who is on this roster?"
Builder team screen sample

Prefer over: separate roster + matches + detail via call_api.

Do not use when: UFC fighters → player_profile; unknown name → resolve_entity first. Dota may return partial roster (API gap). Prefer slug for lol/cod; teamId for cs2.

Parallel-safe: yes. Upstream cost: 2–4. Example: { "game": "lol", "slug": "t1", "recentLimit": 10 }

Input Schema

TableJSON Schema

Name	Required	Description	Default
`game`	Yes	Game title: lol \| cs2 \| dota2 \| cod \| ufc. Tennis has players, not team rosters — use player_profile.
`slug`	No	Team/org slug. Prefer for lol and cod orgs. Pass teamId and/or slug (at least one required). Example: "t1".
`view`	No	Payload weight. Default summary.	summary
`teamId`	No	Team id. Prefer for cs2. Pass teamId and/or slug (at least one required). Either works for dota2.
`recentLimit`	No	Max items to return (default 10, max 25). Example: 10.
`includeFormer`	No	COD roster former players.

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

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 has players, not team rosters — use player_profile."

changedInput schema / properties / game / enum

Previous value: -[
-  "lol",
-  "cs2",
-  "dota2",
-  "cod",
-  "ufc",
-  "tennis"
-]New value: +[
+  "lol",
+  "cs2",
+  "dota2",
+  "cod",
+  "ufc"
+]

First observedSep 1, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the read-only and open-world annotations, the description discloses parallel-safety, upstream cost of 2–4, the Dota partial-roster API gap, and the fact that form/trends/radar are only returned 'when available.' No contradiction with annotations exists.

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?

Every line earns its place: concise summary, direct usage conditions, clear exclusions, known caveat, cost hint, and a concrete example. The structure front-loads the core purpose and then layers decision-relevant guidance.

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 six-parameter tool, the description covers when to use, when not to use, parameter preferences, API limitations, cost, concurrency safety, and includes an example. Combined with the output schema and rich parameter descriptions, nothing critical is missing for an agent to invoke it correctly.

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?

Although schema coverage is already 100%, the description adds valuable selection guidance: prefer slug for lol/cod, teamId for cs2, and note that at least one of teamId/slug is required. The example payload further clarifies how parameters combine.

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 resource and content list: 'Team/org card: identity, roster, recent matches, and form/trends/radar when available.' It also explicitly distinguishes itself from player_profile and call_api, so an agent can tell exactly what this tool covers relative to siblings.

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?

Provides explicit 'When to use' and 'Do not use when' sections, including routing to player_profile for UFC fighters and resolve_entity for unknown names. It also names call_api as an alternative to prefer this tool over, giving clear decision criteria.

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?