Cito API

search_entities

Read-only

Browse/search teams, players, tournaments, events, fighters with type filter and pagination.

When to use:

Typeahead / pickers
"List teams matching…"
Exploring entities without committing to one ID
UFC fighter lookup by name/nickname (uses /ufc/search + client re-rank)

Prefer over resolve_entity when the user wants a list. Prefer resolve_entity when chaining one name into a profile tool.

Do not use when: fetching a known entity profile — use team_profile or player_profile.

UFC: with q set, results are ranked (exact name > multi-token match > nickname). "Jon Jones" should return jon-jones first — never the generic P4P list.

Parallel-safe: yes. Upstream cost: 1–3. Example: { "game": "ufc", "q": "Jon Jones", "type": "fighter", "limit": 10 }

Input Schema

TableJSON Schema

Name	Required	Description	Default
`q`	No	Optional search text.
`game`	Yes	Game title: lol \| cs2 \| dota2 \| cod \| ufc \| tennis. Example: "cs2".
`type`	No	Entity type filter. Example: "team".	any
`limit`	No	Max items to return (default 20, max 50). Example: 20.
`cursor`	No	Opaque cursor from pagination.nextCursor only.
`activeOnly`	No	Prefer active entities when the API supports it.

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

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=true, openWorldHint=true, destructiveHint=false), the description discloses UFC-specific ranking behavior, client-side re-ranking, the guarantee that 'Jon Jones' returns jon-jones first, parallel-safety, and upstream cost. This gives the agent behavioral expectations well beyond what annotations provide.

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 organized into clear sections — purpose, when to use, when not to use, special behavior, and an example. Despite its length, every section earns its place and no information is redundant or filler.

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?

Given six parameters, multiple sibling tools, and an output schema that already documents return shape, the description covers all necessary context: use cases, exclusions, alternative selection, ranking behavior, parallel-safety, cost, and a representative call example. Nothing required for correct invocation 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. The description adds meaning by explaining the q parameter's ranking semantics for UFC, providing a concrete example object, and clarifying that type filters and pagination are core behaviors rather than just schema fields.

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-resource pair: 'Browse/search teams, players, tournaments, events, fighters with type filter and pagination.' It then differentiates itself from resolve_entity, team_profile, and player_profile, so an agent can immediately tell what this tool is for and what it is not.

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?

Usage guidance is explicit and concrete: typeahead/pickers, list requests, entity exploration, and UFC fighter lookup. It also names the preferred alternative for the opposite case ('Prefer resolve_entity when chaining one name into a profile tool') and states a negative rule with the correct sibling tool to use instead.

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.6/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose. Composite tools like match_preview, match_summary, and match_details are well-separated by lifecycle stage, and resolve_entity vs search_entities are differentiated by intended use (single best match vs browsing list). No two tools appear to do the same thing.

Naming Consistency4/5

All names follow snake_case and are descriptive, but the pattern is not strictly verb_noun: most retrieval tools use noun phrases (match_summary, team_profile, standings) while actions use verb_noun (call_api, list_capabilities, resolve_entity). This is consistent within each category, so it remains predictable.

Tool Count4/5

16 tools is slightly above the ideal 3-15 range, but the server covers multiple games (LoL, CS2, UFC, Dota, COD, Tennis) and provides composite tools to reduce upstream calls. Each tool earns its place, and the breadth justifies the count.

Completeness5/5

The tool surface covers health checks, live matches, schedules, profiles, standings, head-to-head, previews, recaps, deep match details, event cards, entity resolution, and includes an escape hatch (call_api) for long-tail paths. No obvious gaps for a read-only sports data API.

Resources

Need Help?