Skip to main content
Glama

List invoices

list_invoices
Read-onlyIdempotent

Retrieve Domeneshop account invoices from the past three years and optionally filter them by payment status.

Instructions

List invoices from the past three years on the Domeneshop account, optionally filtered by 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
statusNoonly return invoices with this status; 'settled' applies only to credit notes

Output Schema

NameRequiredDescriptionDefault
invoicesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.7
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv1.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openBounds, so safety is covered. The description adds a genuinely non-obvious behavioral constraint — results are bounded to the past three years — which materially affects what an agent will and won't find. It does not mention ordering or any result cap, keeping it below a 5.

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 sentence that front-loads the resource and the most surprising constraint (three-year window), with the optional filter trailing. Nothing is wasted.

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, annotations and full schema descriptions supplied, the description only needs to carry the scope and filter intent, and it does. Minor omissions such as result ordering or the meaning of an empty status are not critical for correct invocation.

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 the schema itself explains the status values, including that 'settled' applies only to credit notes. The description only restates 'optionally filtered by status' and adds no semantics (default behavior, empty-string meaning) beyond the schema, so the baseline 3 applies.

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 gives a specific verb and resource ('List invoices') plus the account and time scope, so an agent can immediately tell this is a bulk retrieval rather than the single-item sibling get_invoice. It stops short of naming that sibling explicitly, which is the only thing separating it from a 5.

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: use this to enumerate invoices, optionally narrowed by status, which contrasts implicitly with get_invoice for a single invoice. There is no explicit when-to-use/when-not statement or guidance on alternatives, so the agent must infer the routing.

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