Cito API

cs2_opening_duels

Read-only

First blood and opening duel statistics. Pass playerId to view a pro player's First Kills (FK), First Deaths (FD), and opening duel conversion %, or omit playerId to view the global CS2 opening duel leaderboard.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cs2_opening_duels"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max items to return (default 20, max 100). Example: 20.
`playerId`	No	Optional player ID or slug (e.g. "chucky" or "cs2-player-123"). If omitted, returns global leaderboard.

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.

AddedSep 10, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds useful context about the specific stats (FK, FD, conversion %) but does not disclose additional behavioral traits such as sorting, recency, or response shape; that burden is moderated by the existing annotations and output schema.

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?

A single, well-structured sentence that front-loads the resource and then lays out both usage modes with no filler. Every clause earns its place, and the description avoids restating the tool name or redundant schema details.

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 the tool's simple two-optional-parameter interface, read-only annotations, and existing output schema, the description covers everything an agent needs to decide and call correctly. There is no missing operational context that would lead to misinvocation.

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, but the description adds meaning beyond the schema by naming the returned metrics (First Kills, First Deaths, opening duel conversion %) and explicitly tying playerId to pro-player stats versus the global leaderboard. This helps the agent understand what each call mode will yield.

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 clearly identifies the tool as providing first blood and opening duel statistics, with an explicit verb ('view') and resource (CS2 opening duels). It further distinguishes two distinct modes—player-specific stats versus global leaderboard—making its purpose unambiguous and separable from sibling CS2 tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description clearly explains when to pass playerId versus omit it, giving the agent concrete conditional guidance. It does not explicitly name alternatives or exclusion criteria, but the context is clear enough for a read-only stats tool with a simple two-mode interface.

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?