Skip to main content
Glama

get_credit_transactions

Fetch a history of credit purchases, spends, and adjustments. Use this for auditing or when a user asks about their recent billing history.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of recent records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / default
      Added value: +20
    • changedInput schema / properties / limit / description
      Previous value: -"Number of transactions to return (default 20)"New value: +"Number of recent records to return."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. "Fetch" implies a read-only operation and "history" implies a time-ordered record set, but it does not state ordering, retention window, pagination behavior, or whether the default limit of 20 is the only bound.

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 sentences with no filler: the capability is front-loaded and the usage cue follows. Every sentence earns its place and there is no repetition of the schema.

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 simple, zero-required-parameter read tool with no output schema, the description adequately covers both what is returned (purchases, spends, adjustments) and when to reach for it. Minor gaps remain around record shape and ordering, but nothing critical for 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?

There is a single parameter with 100% schema description coverage ("Number of recent records to return"), so the schema already fully documents it. The description adds no additional constraint, range, or ordering semantics beyond what the schema states, which is the baseline case.

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 opens with a specific verb and resource: "Fetch a history of credit purchases, spends, and adjustments," which clearly delineates this from a balance-check tool like get_credit_balance. It is clear what the tool returns, though it doesn't explicitly name a sibling or state the boundary in those terms.

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 concrete when-to-use guidance: "for auditing or when a user asks about their recent billing history." This gives an agent a clear trigger without any when-not-use exclusions or explicit sibling routing, which keeps it below a 5.

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