AiLinkAny

Get account quota and bounded call statistics

get_usage_stats

Read-onlyIdempotent

Read this OAuth account's quota separately from execution metadata statistics over a named time window. Counts, success/failure, success rate and average terminal duration describe at most 50 metadata records retained for up to 24 hours, never lifetime totals or raw commands. Cold restarts may restore a smaller bounded socket snapshot. No per-call database writes.

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

Input Schema

Name	Required	Description	Default
`window_minutes`	No

Output Schema

Name	Required	Description	Default
`ok`	Yes
`scope`	Yes
`plan_code`	Yes
`starts_at`	Yes
`expires_at`	Yes
`usage_used`	Yes
`usage_limit`	Yes
`generated_at`	Yes
`call_statistics`	Yes
`usage_remaining`	Yes
`subscription_status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

B3.3/5.0

Behavior4/5

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

The annotations already establish that this is a safe read-only, idempotent, non-destructive operation. The description adds substantive behavioral context beyond those annotations: at most 50 records, 24-hour retention, cold-restart snapshot behavior, and no per-call database writes.

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 description is front-loaded with the core purpose and then supplies bounded-data caveats in dense but useful sentences. There is little filler, though the phrasing is somewhat compact and could be clearer for an agent parsing it quickly.

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?

For a read-only statistics tool with an output schema and safety annotations, the description covers the important limitations: bounded retention, snapshot behavior, and no raw commands or lifetime totals. The main gap is the unexplained window_minutes parameter, but the return format is covered by the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter has 0% schema description coverage, so the description must explain it. It only says 'over a named time window' and does not clarify units, default behavior when omitted, or practical bounds beyond the schema's numeric min/max.

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 states a specific verb, resource, and scope: reading this OAuth account's quota plus bounded execution metadata statistics over a time window. It is distinct enough from generic monitoring tools, though it does not explicitly name the sibling tools it differs from.

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

Usage Guidelines2/5

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

The description explains what data is returned and its retention limits, but gives no explicit when-to-use guidance or alternatives such as get_recent_tool_calls or logs_read. The agent must infer the intended use case from the data-scope statements.

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

All AiLinkAny 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?