Skip to main content
Glama

Babelii-Diofis Account

Mutasi saldo saya

account_balance_history
Read-onlyIdempotent

The account's balance ledger, newest first: change, balance after and source of each entry. Up to 50 rows; pass next_before_id as before_id for the next page. 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": "account_balance_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
before_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

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 read-only, idempotent, closed-world and non-destructive, so the description's "Read only" adds nothing there. What it does add beyond structured data is ordering (newest first), a page-size cap (up to 50 rows) and the cursor-paging contract, which are behavioral facts an agent needs and cannot get from the annotations.

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?

Three short clauses, front-loaded with the resource and row shape, followed by pagination and the safety note. No filler; the field enumeration is slightly compressed into a single clause but remains parseable.

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 two-parameter read tool with an output schema, this covers resource, ordering, page cap, and the paging handoff to the next call. Return-field details partly duplicate the output schema, and the limit parameter's behaviour is left under-specified, but nothing critical to correct invocation is missing.

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 0%, so the description must carry the parameter meaning. It explains before_id well by tying it to the response field next_before_id, but limit is only indirectly implied by "Up to 50 rows" and its default of 20 is never discussed, leaving half the parameters under-documented.

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?

Names a specific resource and scope: "The account's balance ledger, newest first", and enumerates what each entry contains (change, balance after, source). It is clearly distinct from an overview or topups listing by virtue of being a paginated ledger, though it does not explicitly name a sibling for contrast.

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 rather than stated: an agent can infer this is the tool for a paginated transaction list. The only procedural guidance is pagination ("pass next_before_id as before_id for the next page"), with no when-to-use/when-not or comparison to an alternative source of balance information.

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