Skip to main content
Glama

List invoices

list_invoices
Read-only

Retrieve invoices created with your credentials, sorted newest first and showing paid or unpaid status. Filter by wallet address and paginate results to track crypto payment requests.

Instructions

List invoices created with these credentials, newest first, with paid/unpaid status.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
walletAddressNoOnly invoices paid to this wallet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful traits beyond that — credential-scoped results, newest-first ordering, and paid/unpaid status in results. It omits pagination behavior, default page size, and what happens when there are no results.

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?

A single front-loaded sentence with no filler; every clause (credentials scope, ordering, status) contributes distinct information.

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?

Adequate for a simple read-only list tool with annotations handling safety and no output schema to explain. Still missing pagination semantics (default limit, max 100, whether offset pages backward given newest-first sort) that an agent needs to call it reliably.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only walletAddress has schema documentation (33% coverage); limit and offset carry only type/range bounds with no descriptions or defaults. The description's 'newest first' hints at ordering relevant to offset but adds no syntax, default-limit, or max-page meaning, so the coverage gap is not compensated.

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?

Specific verb plus resource ("List invoices") with meaningful scope qualifiers: created with these credentials, sorted newest first, and including paid/unpaid status. This distinguishes it from single-record siblings like check_invoice or create_invoice, though it never names them explicitly.

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

Usage Guidelines2/5

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

No when-to-use guidance beyond the implied 'listing' behavior, no exclusions, and no mention of when to prefer find/get siblings. An agent must infer that this is the bulk-listing tool and check_invoice is for a single invoice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.