Skip to main content
Glama

credits.list_history

List the project owner's credit history, newest first: purchases, assistant usage, renders and AI generations, each with its signed amount in milli-credits (1000 = 1 credit; negative = spent), balance after, detail (model, resolution, tokens…) and the project it was for. Also returns net spend per category over the last 30 days. Pass nextCursor back as cursor for older entries.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "credits.list_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
categoryNo
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and largely meets it: it declares ordering (newest first), units (milli-credits, 1000 = 1 credit, negative = spent), that a running 'balance after' is included, and that a 30-day per-category net spend summary is also returned. What it omits is retention/window for the history itself and any permission or ownership requirements for reading another project's credits.

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 dense paragraph that front-loads the verb and resource before the return-shape detail. Every clause adds information, though the parenthetical 'detail (model, resolution, tokens…)' is slightly vague and the 30-day summary sentence could be ordered more prominently.

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 four-parameter read tool with no annotations and no output schema, the description covers return values, units, ordering, and pagination well enough to call it correctly. The remaining gap is the undocumented limit parameter and no statement of the history's time window or access requirements.

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 0%, so the description must compensate, and it does for three of four parameters: cursor is explained via the nextCursor round-trip, the category enum values map to the enumerated entry types, and projectId is implicit in 'the project it was for'. The limit parameter (1-100) is never mentioned, leaving its default and effect undocumented.

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 project owner's credit history') and enumerates its scope (purchases, assistant usage, renders, AI generations). An agent can immediately distinguish this from the sibling credits.get_balance, which only returns a current balance.

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: 'newest first' plus 'Pass nextCursor back as cursor for older entries' describes pagination behavior but never states when to prefer this over credits.get_balance or when a history lookup is warranted. No exclusions or explicit alternative routing are provided.

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.