Skip to main content
Glama

Get billing standing

get_billing_standing
Read-only

The organisation's billing standing as the platform's gates read it (the twin of ankra org billing standing): which ladder applies - an overdue invoice, the credit limit, an exhausted prepaid wallet, or the free tier's included capacity - whether it is enforced or still shadowed, the copy naming the remedy, and the actions it pauses. Use this when an action was refused with a payment-required error or the user asks why growth is paused. Requires billing.read. Read-only.

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_billing_standing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and the description restates read-only, which is redundant, but it adds genuinely new behavior context: a required `billing.read` scope, the fact that this reflects what the platform's gates read, and the enforced-vs-shadowed distinction including which actions are paused. With annotations covering the safety profile, this extra disclosure puts it solidly above baseline, though it says nothing about caching, freshness, or response shape.

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?

Front-loaded with what the standing contains, then the usage trigger, then the permission requirement. Two sentences carry a lot without filler. The first sentence is dense with em-dash enumeration and takes slightly more parsing than ideal, but every clause adds information.

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?

No input parameters and no output schema, so the description bears the burden of describing the returned content — and it does, listing the ladder type, enforcement state, remedy message, and paused actions. The auth requirement is also stated, so an agent has everything needed to call it and interpret the result.

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 takes zero parameters, so there is no parameter meaning to convey and nothing for the description to compensate for. Baseline 4 applies; no parameter claims are made that could mislead.

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?

States a specific verb+resource ('the organisation's billing standing') and enumerates exactly what the answer contains: which ladder applies (overdue invoice, credit limit, exhausted prepaid wallet, free-tier capacity), enforced vs shadowed, remedy copy, and paused actions. It also maps to the CLI twin `ankra org billing standing`. It does not explicitly differentiate from nearby billing/cost siblings such as get_wallet_balance or get_usage, which keeps it below a 5.

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

Usage Guidelines4/5

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

Gives concrete triggering conditions: an action refused with a payment-required error, or a user asking why growth is paused. That is clear context for invocation. It lacks explicit when-not-to-use guidance or a named alternative for related questions (e.g. raw wallet balance vs. gate standing).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.