Skip to main content
Glama

list_transactions

List the caller's token wallet ledger transactions (type, amount, context, time, linked job), newest first, paginated with limit (default 20, cap 96) and offset, and sorted by occurred_at, amount or transaction_type with order. Use it to see where tokens went, one entry per movement; for the current balance use check_balance, and for aggregate verification counts use get_usage. Requires the billing:read scope.

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

Input Schema

NameRequiredDescriptionDefault
sortNoOrder by occurred_at (default), amount or transaction_type.
limitNoNumber of transactions to return (API default 20, cap 96).
orderNoOrder direction: desc (default) or asc.
offsetNoNumber of transactions to skip (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / order
      Added value: +{
      +  "description": "Order direction: desc (default) or asc.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "Order by occurred_at (default), amount or transaction_type.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose useful behavior: newest-first default ordering, pagination defaults and the 96 cap, the sort dimensions, and that it requires the billing:read scope. It does not state what happens past the offset cap, any rate limits, or the exact response envelope, so a 3 is fair for a read tool whose behavior is mostly implied by 'List'.

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?

It is front-loaded with the resource and returned fields, then alternatives, then the auth requirement in a single dense paragraph with no filler. The first sentence is heavily packed with parentheticals, which slightly hurts scannability but every clause carries real information.

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?

There is no output schema and no annotations, but the description compensates by listing the ledger fields returned, the ordering/pagination semantics, and the required scope. Remaining gaps (response shape, error behavior at limits) are minor for a straightforward paginated list tool.

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?

Schema description coverage is 100%, so the schema already documents all four parameters; the description reinforces the defaults (limit 20/cap 96, offset 0, occurred_at default) and adds the context that sorting works together with an order direction, though it introduces no meaning the schema lacks.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('List the caller's token wallet ledger transactions') and enumerates the returned fields (type, amount, context, time, linked job), which lets an agent distinguish it from check_balance and get_usage without opening any schema.

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

Usage Guidelines5/5

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

It explicitly routes the agent: this tool shows 'where tokens went, one entry per movement', while 'for the current balance use check_balance' and 'for aggregate verification counts use get_usage'. That is a clear when-to-use plus named alternatives with the conditions that select them.

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