Cito API

valorant_transfers

Read-only

Recent Valorant roster transfers, signings, departures, and benchings with optional team, player, action, and date filters.

When to use:

"Recent Valorant roster moves"
"Who joined or left Sentinels?"
Tracking player transfers within a date window

Prefer over: call_api for /valorant/transfers.

Parallel-safe: yes. Upstream cost: 1.

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": "valorant_transfers"
  }
}

Input Schema

Name	Required	Description
`to`	No	End move_date inclusive (YYYY-MM-DD).
`from`	No	Start move_date inclusive (YYYY-MM-DD).
`team`	No	Filter by team id (e.g. "val-team-2") or team name.
`limit`	No	Max items to return (default 25, max 100). Example: 25.
`action`	No	Filter by move action (e.g. "join", "leave", "inactive").
`offset`	No	Pagination offset (default 0).
`player`	No	Filter by player id (e.g. "val-player-123") or handle.

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.

AddedNov 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower, and the description still contributes non-annotation facts: it is parallel-safe and costs 1 upstream call. It stops short of describing how the unfiltered default behaves (what 'recent' means with no filters) or how results are ordered, which would round out the behavioral picture.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core sentence is front-loaded and the operational facts are compact, single-purpose lines. The when-to-use bullets partially restate the opening sentence's coverage, which is mild redundancy, but nothing is padded or buried.

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 7 all-optional parameters, a 100% covered schema, an output schema, and annotations present, the description supplies what the structured fields cannot: routing guidance, parallelism, and cost. The only gap is the semantics of the no-filter default, which an agent calling with all-optional params would benefit from knowing.

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 description coverage is 100%, so every parameter already carries format, defaults, bounds, and examples in the schema. The description only mirrors the filter categories (team, player, action, date) without adding syntax, matching behavior, or combination semantics beyond what the schema states. Baseline 3 applies when the schema does the heavy lifting.

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 resource and verb: 'Recent Valorant roster transfers, signings, departures, and benchings', then enumerates the filterable dimensions. The Valorant qualifier and the explicit 'Prefer over: call_api for /valorant/transfers' line separate it from both the generic API escape hatch and the CS2 sibling without the agent needing to open a 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?

Provides explicit when-to-use triggers ('Who joined or left Sentinels?', tracking transfers within a date window) and an explicit routing rule naming the alternative it supersedes. Both the use case and the preferred-vs-alternative decision are stated rather than inferred.

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?