--deprecated

This connector has been deprecated

Replaced by io.github.no-fait/infinite-audience

Check Subscription Capacity

check_balance

Read-onlyIdempotent

Read the organization subscription capacity, reserved and pending consumption, replenishment status, and snapshot freshness. For an agency-managed organization, the response describes its attributed subscription consumption. Requires 'account-read' scope.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`billing`	Yes
`guidance`	No	Interpretation or recovery guidance for this result
`count_unit`	No
`page_count`	No	Number of objects on this page, not the organization total
`count_state`	No	Unknown means no count; available does not guarantee freshness. Recount for a current value.
`operational`	Yes
`billing_mode`	Yes	Subscription capacity routing mode; native_setup_required indicates setup is pending
`next_actions`	No	Suggested next calls using returned IDs and available scopes. Not executed and not user consent.
`money_display`	No	Formatted subscription capacity amounts with currency labels, ready to display without further conversion. Unavailable amounts are omitted; zero amounts are included.
`population_input`	No	Population input used for the preview; IDs refer to their current saved definitions

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds useful behavioral context beyond annotations: agency-managed organizations return attributed consumption, and the call requires 'account-read' scope. Rate limits or pagination are not covered, but the output schema exists.

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?

The description is two sentences and front-loads what is read before adding the agency-managed nuance and required scope. It is appropriately sized with no redundant wording.

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 zero-parameter read-only tool with an output schema and strong annotations, the description covers the returned data, agency-managed behavior, and auth scope. The main missing context is sibling differentiation, which would help an agent route correctly but is not required for invocation.

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?

The tool has zero input parameters, so there are no parameter semantics to document; this is the baseline case. The description appropriately does not waste space discussing parameters that do not 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 states a specific verb, 'Read', and names concrete resources: organization subscription capacity, reserved and pending consumption, replenishment status, and snapshot freshness. It is clear what the tool does, though it does not explicitly distinguish itself from siblings like get_account_usage or check_topup_status.

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 provides no when-to-use guidance and no alternatives or exclusions. It states a permission requirement, but an agent still cannot tell from the definition when this tool should be chosen over get_account_usage or check_topup_status.

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

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