Skip to main content
Glama

list_credit_transactions

Read-onlyIdempotent

Read your credit ledger and current balance (up to 100 entries).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is fully covered without the description. The description does add one piece of behavioral context beyond annotations — the 'up to 100 entries' cap — but says nothing about ordering, pagination behavior, or rate/credit-refresh timing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that identifies the resource, the returned data, and the result cap with zero filler. Nothing could be removed without losing 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?

For a two-optional-parameter read tool with no output schema and full annotation coverage, the description covers the essential questions: what is read, what is returned (ledger plus current balance), and how much can come back. Only the pagination contract and transaction field contents are left unstated, which is acceptable given there is no output schema to duplicate.

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 schema gives bare 'Limit' and 'Offset' integers with defaults and no meaning. The description partially compensates by implying a 100-entry ceiling, which bounds the practical value of 'limit', but it never explains offset, ordering, or what a page represents.

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?

States a specific verb and resource: 'Read your credit ledger and current balance'. An agent can tell this is a read-only billing/credits query and distinguish it from the upload and generation siblings without opening the schema. It stops short of any explicit sibling contrast, which keeps it from a 5.

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: you call it to check balance or transaction history. There are no explicit when-to-use/when-not conditions or named alternatives, though no sibling appears to serve the same purpose, so the missing guidance is minor.

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