Skip to main content
Glama

List invoices

invoice_list
Read-onlyIdempotent

This organisation's invoices, newest first: number, dates, total, amount paid, balance due and status. Filter by status or invoice date range. No PDFs. Read only.

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
toNoISO date, inclusive
fromNoISO date, inclusive
pageNo
sizeNoDefault 20
statusNoe.g. DRAFT, ISSUED, PAID, OVERDUE

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the safety profile is covered; the description nonetheless adds real context with the newest-first ordering, the inventory of fields returned, and the explicit 'No PDFs' limitation. It does not explain pagination or result-count behavior, but 'Read only' merely echoes the annotation.

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 compact sentences plus two fragments, with the identity of the resource and the field inventory front-loaded before the filtering hints. No sentence is wasted, though the trailing 'Read only' fragment duplicates the annotation.

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 usefully fills that gap by enumerating the returned fields and the sort order, and all five optional parameters are covered by schema descriptions. Only pagination behavior and the list-vs-detail boundary remain unaddressed for a tool of this complexity.

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 80%, so the schema already documents to/from as inclusive ISO dates, status examples, and the size default of 20. The description's 'filter by status or invoice date range' only restates those parameters without adding format or combination rules, which matches the baseline for a well-covered schema.

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?

States the resource (this organisation's invoices), the ordering (newest first), the fields returned, and the filtering dimensions. 'No PDFs' implicitly separates it from an invoice_detail-style tool, though the sibling is never named, so the differentiation is inferential rather than explicit.

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?

The description makes clear this is the filtered-list entry point and that status and date-range filtering are supported, which implies when to reach for it. It never states when not to use it or points to invoice_detail for the full record, leaving the boundary between list and detail to the agent's inference.

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.