Gangway AIS

Credits and plan

account_usage

Read-onlyIdempotent

Your key's plan, the credits used and left this month, when they renew, and the plan's rate, largest box, reach back and delay. Free. Free accounts too: their answers are 24 hours behind, with a box of at most 1 square degree and 1,000 credits a month; paid plans are live.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish a safe, idempotent, read-only lookup. The description adds concrete return contents and tier-dependent behavior: free accounts are 24 hours behind with a 1-square-degree box and 1,000 credits/month, while paid plans are live. It does not explain authentication beyond 'your key's', but it adds substantial context 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.

Conciseness3/5

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

The description is compact and front-loads the returned fields, but the prose is fragmented. 'Free. Free accounts too:' reads as an ambiguous run-on list, weakening structure.

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 no output schema and no parameters, the description must explain what comes back, and it covers the main fields plus free-versus-paid behavior. Terms such as 'largest box', 'reach back', and 'delay' are not fully defined, and units are only implied for the free box.

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?

There are zero parameters and the schema is empty. Under the rubric this is the baseline of 4; the description adds no parameter meaning because none exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as the API key's plan and credit status, including renewal timing and plan limits. The retrieval purpose is clear, but it is phrased as a noun list rather than a verb and does not explicitly distinguish itself from siblings.

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

Usage Guidelines3/5

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

The description implies use when checking plan, remaining credits, renewal, or limits, and its free-account notes show what restrictions apply. It provides no explicit when-to-use, when-not, or named alternative, so usage is inferred from the purpose.

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

All Gangway AIS 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?