Skip to main content
Glama

billing_attempts

Read-only

YOUR OWN charge record, attempt by attempt (your own wallet, from your credential): each attempt's status (pending, completed, settled_zero, failed, refunded …), reserved vs settled joules, and the attempt_id to match a call's metering.attempt_id. Paged with limit and offset.

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": "billing_attempts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows to return. 1-200. Default 50.
offsetNoRows to skip, for paging. Default 0.

Output Schema

NameRequiredDescriptionDefault
noteNo
countNo
itemsNo
statusesNo
wallet_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changed
    • removedInput schema / properties / limit / default
      Removed value: -null
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / offset / default
      Removed value: -null
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
    • removedInput schema / title
      Removed value: -"billing_attemptsArguments"
    • removedOutput schema / description
      Removed value: -"billing_attempts — the caller's own charge record (GET /api/v1/billing/attempts): items[] of\n{attempt_id, when, settled_at, endpoint, query_type, status, reserved_joules, settled_joules,\nsettled_all_in_joules, idempotency_key, transfer_id, detail} + count + wallet_id + a statuses legend.\nItems stay opaque (list[Any]) so a backend field this relay does not model passes through verbatim."
    • removedOutput schema / properties / count / default
      Removed value: -null
    • removedOutput schema / properties / count / title
      Removed value: -"Count"
    • removedOutput schema / properties / items / default
      Removed value: -null
    • removedOutput schema / properties / items / title
      Removed value: -"Items"
    • removedOutput schema / properties / note / default
      Removed value: -null
    • removedOutput schema / properties / note / title
      Removed value: -"Note"
    • removedOutput schema / properties / statuses / default
      Removed value: -null
    • removedOutput schema / properties / statuses / title
      Removed value: -"Statuses"
    • removedOutput schema / properties / wallet_id / default
      Removed value: -null
    • removedOutput schema / properties / wallet_id / title
      Removed value: -"Wallet Id"
    • removedOutput schema / title
      Removed value: -"AttemptsOut"
  2. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows to return. 1-200. Default 50."
    • addedInput schema / properties / offset / description
      Added value: +"Rows to skip, for paging. Default 0."
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/non-destructive/closed-world, and the description adds real context: results are scoped to your own wallet and credential only (no cross-wallet visibility), the status vocabulary is listed, and reserved-vs-settled joules is called out. Pagination defaults are left to the schema rather than contradicted.

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?

Two sentences, front-loaded with the scoping claim, and the dangling '…' after the status list is a minor sloppiness. Nearly every clause (own wallet, statuses, joules fields, attempt_id join, paging) carries 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?

With an output schema present, the description does not need to explain return shapes, yet it still highlights the fields an agent will care about and how attempt_id links to metering. Combined with annotations covering safety, an agent has enough to call this correctly.

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 both parameters carry their own descriptions (range, defaults), so 'Paged with limit and offset' is a restatement rather than added meaning. Baseline 3 applies when the schema already does the heavy lifting.

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?

Names a specific resource and scope: the caller's OWN charge attempts, pulled from their own wallet/credential, with the returned fields enumerated (status, reserved vs settled joules, attempt_id). The read/list verb is only implied by 'Paged with limit and offset', but the resource is unambiguous against siblings like deposits, trade_settlement, and billing_quote.

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?

Gives clear context for when to reach for it: inspecting your own billing attempts and resolving an attempt_id seen in a call's `metering.attempt_id`. It never names a competing sibling or an exclusion, so it stops short of full when/when-not guidance.

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