Skip to main content
Glama

This month's usage and charges

billing_summary
Read-onlyIdempotent

Usage and charges for a month (default: this month to date) by channel, the account's opening and closing balance, outstanding invoices, and the most recent wallet transactions (top-ups and debits). 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": "billing_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthNoe.g. "2026-10". Default the current month
transactionsNoHow many recent wallet transactions, default 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the trailing 'Read only.' mostly restates them. What the description does add is genuinely useful scope: the tool aggregates several sections in one call and defaults to the current month-to-date, which tells the agent no mutation or side effects are possible.

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?

A single front-loaded sentence that names the resource and its scope first, then lists contents in a compact parenthetical. No filler, though the dense enumerated list in one sentence is slightly harder to scan than a short bulleted breakdown would be.

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, the enumeration of returned sections is exactly the right compensation, and both optional parameters are fully documented. The remaining gap is minor: it does not say whether the outstanding-invoice or transaction lists are truncated, or what happens for a month with no activity.

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 schema already gives the YYYY-MM pattern example and the default of 10 transactions (max 20). The description's 'default: this month to date' adds only slight framing beyond the schema's 'Default the current month', so this sits at the baseline rather than above it.

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 pairs a specific verb with a concrete resource and enumerates the returned sections: per-channel usage and charges, opening/closing balance, outstanding invoices, and recent wallet transactions. An agent can tell this is a billing/account-financials read rather than a call-metrics tool, even though it never names a sibling to contrast with.

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?

Usage is implied by the enumerated contents and the 'default: this month to date' note, so an agent can infer it is the first stop for a monthly financial overview. There is no explicit when-to-use or when-not guidance, and nothing routes the agent to invoice_list/invoice_detail for drilling into individual invoices.

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.