Skip to main content
Glama

invoice_list

Read-onlyIdempotent

Lists your invoices, newest first (200 at most; pass limit and cursor to page). Every row carries the same worked-out money and state as invoice_read: total_cents, remaining_cents, state, is_overdue, days_overdue (integer CENTS, business days). To find what to chase, pass state 'overdue': only invoices issued, still owed and due before today in the business time zone come back. payer_confirmations_pending counts the payer's "I've paid" reports waiting on each row. Refuses an unlisted state, a limit outside 1-200 or a malformed cursor with VALIDATION_ERROR: resend with a listed state, without limit, or with next_cursor exactly as returned.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size 1-200. Omit BOTH limit and cursor for the legacy bare-array first page of 200; pass either to get { items, next_cursor, limit } instead.
stateNoOnly invoices in this worked-out state, still newest first and paged the same way. Leave it out for every invoice.
cursorNoOpaque page cursor — pass a previous response's next_cursor verbatim. null next_cursor means no further pages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, which establish a safe idempotent read, the description discloses the 200-row cap, cursor paging, validation failures and exact remedies, overdue-state semantics, and additional row fields such as payer_confirmations_pending. This is unusually rich behavioral context for an agent.

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?

The description is dense but front-loaded with the core list behavior, then adds only operationally useful details about row fields, overdue filtering, and validation recovery. Every sentence provides information an agent needs to call or recover the tool correctly.

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 no output schema, the description does a good job naming the row fields and paging behavior, but it does not explain the legacy bare-array response shape that appears in the limit parameter schema. That is a minor completeness gap rather than a blocking omission.

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 coverage is 100%, so the baseline is 3, but the description adds meaningful semantics for the state parameter, especially that 'overdue' means issued, still owed, and due before today in the business time zone. It also reinforces the limit range and cursor-verbatim behavior, though it does not further explain each enum state.

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 states a specific verb and resource: it lists the tenant's invoices, newest first, with paging and state filtering. It also distinguishes the row shape from invoice_read and calls out the overdue use case, so an agent can identify the tool's role among invoice siblings.

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 gives clear usage context for the overdue state ('To find what to chase') and explains how to recover from validation errors. It does not explicitly compare itself with invoice_search or invoice_read as alternatives, but the main operational context is clear.

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