Cito API

by com.citoapi.api

Overview Discussions Admin

call_api

Read-only

Power escape hatch: allowlisted Cito REST call with unshaped raw JSON in data.raw.

When to use:

Long-tail paths not yet curated (Fortnite, CS2 leaderboards, niche stats)
Debugging payloads while building an app
User explicitly knows an OpenAPI path

Prefer curated tools for all standard jobs (live, schedule, profiles, standings, H2H, previews).

Do not use when: a curated tool covers the outcome. Avoid parallel storms; same plan rate limits apply.

Path must start with / and match allowlisted prefixes: /health, /lol, /cs2, /dota2, /cod, /ufc, /fortnite, /tennis, /valorant. Rejects absolute URLs and path traversal → PATH_NOT_ALLOWED.

Parallel-safe: yes but discouraged in bulk. Upstream cost: 1. Example: { "method": "GET", "path": "/cs2/rankings/teams", "queryJson": "{"page":1,"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": {
      "path": "<path>"
    },
    "name": "call_api"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Path starting with /. Allowlisted prefixes only. Example: "/cs2/rankings/teams".
`query`	No	Query params as a plain object (alternative to queryJson). Example: {"year":2026}.
`method`	No	HTTP method. GET only: call_api is read-only. Example: "GET".	GET
`queryJson`	No	Stringified JSON object of query params. Example: "{\"page\":1,\"limit\":20}".	{}

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.

Changed3 schema fields changedSep 15, 2026

removedInput schema / properties / bodyJson

Removed value: -{
-  "description": "Stringified JSON body for POST only (rare).",
-  "type": "string"
-}

changedInput schema / properties / method / description

Previous value: -"HTTP method. Prefer GET. Example: \"GET\"."New value: +"HTTP method. GET only: call_api is read-only. Example: \"GET\"."

changedInput schema / properties / method / enum

Previous value: -[
-  "GET",
-  "POST"
-]New value: +[
+  "GET"
+]

First observedSep 1, 2026

TDQS

A4.6/5.0

Behavior4/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 covered. The description still adds real context beyond them: the allowlist enforcement, the PATH_NOT_ALLOWED rejection for absolute URLs and traversal, shared plan rate limits, and an upstream cost of 1. It stops short of describing response shape, but an output schema exists to carry that.

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?

It is front-loaded with the one-line purpose before any bullets, and the when/when-not structure is scannable. A few items duplicate the schema verbatim, notably the /cs2/rankings/teams example repeated in both the description and the path/queryJson fields, which is mild waste but not enough to hurt usability.

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 an open-world escape-hatch tool, the description covers the constraints an agent could plausibly get wrong: path format, prefix allowlist, the rejection code, method restriction to GET, and cost/rate-limit expectations. With an output schema present, it need not explain return values, and nothing material is left unstated.

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 the actual allowlisted prefix list (/health, /lol, /cs2, /dota2, /cod, /ufc, /fortnite, /tennis, /valorant) that the schema only gestures at with 'Allowlisted prefixes only'. The worked example also clarifies how queryJson is serialized alongside the plain-object query alternative.

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 names a specific verb and resource — an allowlisted raw REST call — and frames it explicitly as an escape hatch returning unshaped JSON in data.raw. That framing immediately separates it from the curated, shaped siblings like standings, match_details, and player_profile.

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?

It gives three concrete when-to-use cases (long-tail paths, debugging payloads, user knows an OpenAPI path) plus an explicit prefer-curated rule and a 'Do not use when: a curated tool covers the outcome' exclusion. It also warns against parallel storms, which is guidance an agent would not otherwise have.

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?