Skip to main content
Glama

Get Usage History

get_usage_history
Read-onlyIdempotent

[Meta · free] Return recent credit_ledger transactions for the authenticated user. Filter by tool name, reason, or date range. Paginated. Free.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return
reasonNoFilter by ledger reason
date_toNoEnd date (ISO 8601)
date_fromNoStart date (ISO 8601)
tool_nameNoFilter to a specific MCP tool

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered elsewhere. The description adds real context beyond that: authenticated-user scoping, a 'recent' (implicitly bounded) window, the credit_ledger source, and that calls are free. However, 'Paginated' is asserted without a cursor or offset parameter in the schema, leaving the pagination mechanic unexplained, and the returned record fields are never characterized.

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?

Three short front-loaded sentences plus the meta tag; the resource and scope come first and nothing is buried. 'Free' appears twice — in the '[Meta · free]' tag and again as a trailing sentence — which is minor redundancy. Overall it is tight and easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter, all-optional read tool with no output schema, the description establishes scope and filters but never describes the shape of a ledger transaction, which is the main thing an agent needs to interpret results. The 'Paginated' claim is also unsupported by any offset/cursor parameter. Adequate to invoke, incomplete for consuming the output.

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 100%, so every parameter including the reason enum is already documented in the schema and the baseline applies. The description only restates the filterable dimensions ('tool name, reason, or date range') without adding format, default, or interaction guidance. It is marginally useful for orienting the reader but adds little beyond the structured fields.

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 states a specific verb and resource — 'Return recent credit_ledger transactions for the authenticated user' — which is clearly distinct from the sibling get_credit_balance (a balance read, not a ledger listing). It also names the filterable dimensions, so an agent knows what kind of query this is. It stops short of explicitly contrasting itself with the closest sibling, which keeps it out of the 5 range.

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 by the subject matter: use this to inspect past credit transactions filtered by tool, reason, or date. There is no explicit statement of when to prefer this over get_credit_balance or get_cost_estimate, and no stated exclusions. An agent can infer the use case but is given no routing rule.

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