Skip to main content
Glama

Credit history

get_credit_history
Read-onlyIdempotent

Lists the latest credit changes, newest first: images made, refunds for failed or cancelled images, credits bought or added, expiries. Free. Use it to answer "where did my credits go?".

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many entries (default 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish the read-only, idempotent, non-destructive, closed-world profile, so the description only needs to add context — and it does: newest-first ordering, the categories of entries returned, and the fact that the call is free. It does not describe pagination behavior or what fields each entry carries, which leaves a modest gap.

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?

Two short sentences with zero filler: the primary behavior and entry types come first, then the practical use case. Every clause earns its place.

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 description does the work of telling the agent what comes back by listing entry types and ordering, which is the essential information for interpreting results. It omits whether entries include timestamps or credit deltas and how to page beyond the limit, minor gaps for a one-parameter read tool.

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 coverage is 100% and the single optional 'limit' parameter is fully documented in the schema, including its default of 50 and the maximum of 200. The description adds no further semantics about the limit or how it interacts with ordering, so the baseline of 3 applies.

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 gives a specific verb and resource ('Lists the latest credit changes') and enumerates the entry types covered (images made, refunds, credits bought/added, expiries), which separates it from the balance-checking sibling. It never names get_credit_balance explicitly, so the differentiation is implied through the 'where did my credits go?' framing rather than stated.

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

Usage Guidelines4/5

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

It supplies a concrete use case in the form of a user question ('where did my credits go?'), which gives an agent a clear trigger for selecting this tool. It stops short of naming alternatives such as get_credit_balance or stating when this tool is the wrong choice.

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.