Skip to main content
Glama

Balance history

get_balance_history
Read-onlyIdempotent

The account's balance lines, newest first: top-ups, grants and charges (search, facts on request, outreach) in whole credits, with the search each charge was for. [REST: GET /api/account/balance/history]

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral facts: results are ordered newest first, amounts are in whole credits, and each charge carries the search it belongs to; it even cites the backing REST endpoint. It omits that only the newest N lines are returned with no paging cursor, which matters given the limit cap.

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 carries the resource, contents, ordering, unit and linkage, followed by a compact REST reference. The nested parentheticals make it denser than necessary but nothing is redundant.

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 one-parameter read-only tool with rich annotations and no output schema, the description covers what the returned lines are and how they are ordered, which is most of what an agent needs. The remaining gap is truncation behavior and the meaning of the returned per-line fields, which nothing else in the definition documents.

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?

There is one parameter (limit) with 0% schema description coverage, so the description carries the burden but never mentions it. The 'newest first' framing does imply that limit truncates to the most recent lines, which is real added meaning, but the default of 50, the maximum of 200 and the absence of paging are only conveyed by the schema.

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 the resource (the account's balance lines), the record types it contains (top-ups, grants, charges) and the ordering (newest first), so an agent knows exactly what this returns. It does not explicitly distinguish itself from siblings such as get_account or get_payment_status, leaving the balance-vs-history distinction to inference.

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 only implied: an agent can infer this is the line-item ledger behind the account balance, but the description never states when to call it instead of get_account or get_payment_status, nor any prerequisites. The parenthetical listing of charge categories (search, facts on request, outreach) gives a hint about what is covered but is not framed as guidance.

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