Skip to main content
Glama

Cito API

by com.citoapi.api
OverviewDiscussionsAdmin

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, /raf, /bkfc. 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}" }

Input Schema

NameRequiredDescriptionDefault
pathYesPath starting with /. Allowlisted prefixes only. Example: "/cs2/rankings/teams".
queryNoQuery params as a plain object (alternative to queryJson). Example: {"year":2026}.
methodNoHTTP method. GET only: call_api is read-only. Example: "GET".GET
queryJsonNoStringified JSON object of query params. Example: "{\"page\":1,\"limit\":20}".{}

Output Schema

NameRequiredDescriptionDefault
okYestrue if the tool succeeded
dataNoResult payload when ok is true; null on error
metaYes
errorNo
partialNo
paginationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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"
+]
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds substantial extra context: the allowlist mechanism, rejection behavior producing PATH_NOT_ALLOWED, the upstream cost of 1, and the caution against bulk parallelism. That is meaningful behavior beyond the annotations.

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?

Front-loaded one-line purpose followed by scannable when-to-use, when-not-to-use, constraints, and a single example. Every section adds information; nothing is 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?

For a complex open-world escape-hatch tool, the description covers allowlist constraints, error behavior, cost, parallelism caution, and a full example, while an output schema exists to cover return values. An agent has everything needed to invoke correctly.

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 nonetheless adds path-prefix constraints and a worked example that maps path/queryJson usage concretely. It does not explain the query-vs-queryJson alternative, which keeps it from a 5.

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 states it is an 'allowlisted Cito REST call with unshaped raw JSON in data.raw', a specific verb plus scope. It clearly distinguishes itself from the many curated siblings by framing itself as the escape hatch for paths those tools do not cover.

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 lists explicit when-to-use cases (long-tail paths, debugging, user-known OpenAPI path), a redirect preference ('prefer curated tools'), and an explicit when-not-to-use ('avoid when a curated tool covers the outcome'), plus a parallel-storm warning. This is as complete as usage guidance gets.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Cito API toolsInspect
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