Skip to main content
Glama

ExducerAI GPU cloud

Balance and ledger

get_billing
Read-onlyIdempotent

The prepaid balance and the most recent credit ledger lines (top-ups and charges) in CAD.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many ledger lines, newest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds useful context beyond that — the ledger is currency-denominated in CAD and consists of top-ups and charges — but says nothing about auth requirements, freshness of the balance, or ordering beyond what the limit parameter implies.

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?

One compact sentence with no filler, and the primary subject (prepaid balance) is front-loaded before the ledger detail. It is a noun phrase rather than a sentence with an explicit verb, which is the only structural weakness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only tool with full annotation coverage this is nearly enough, but there is no output schema, so the description carries the burden of describing the return shape. It names balance and ledger lines and the currency but does not say what fields a ledger line contains or whether the balance is signed or credit-based.

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

Parameters3/5

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

Schema description coverage is 100% and the single limit parameter is fully documented in the schema, including default, min/max and newest-first semantics. The description's 'most recent' phrasing corroborates but does not extend the schema, so the baseline 3 applies.

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 names a specific resource pair — prepaid balance and recent credit ledger lines — and even characterizes the line types (top-ups and charges) and currency (CAD). It is clearly distinguishable from list_invoices and get_usage, though it never explicitly contrasts itself with them.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of the sibling tools that answer adjacent questions (get_usage, get_pricing, list_invoices). The agent must infer that this is the balance-checking tool from the description alone.

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.

Resources