Skip to main content
Glama

Facturen

list_invoices
Read-only

Retrieve invoices filtered by year or status (concept, open, past due, paid) to review billing records and outstanding payments.

Instructions

List invoices, optionally for one year or one status: concept, open, "te laat" (past the due date) or betaald.

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
yearNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The supplied annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only the domain meaning that "te laat" means past the due date; it says nothing about sort order, paging, or result volume, which are the remaining behavioral unknowns for a list tool.

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?

One front-loaded sentence that names the resource first and the optional filters second, with no filler. Every clause carries a fact the agent needs, and the inline gloss on "te laat" earns its space.

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?

For a two-parameter, non-destructive read tool with annotations covering safety and no output schema, this is close to sufficient. The only real gap is the absence of any note on ordering or scope of returned invoices, which for a listing tool an agent may want to know.

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 description coverage is 0%, so the description must carry parameter meaning and it largely does: it identifies the year filter and enumerates all four status values, and it glosses "te laat" as past the due date, which a bare enum cannot convey. It falls short of a 5 because it does not clarify the year format or what a combined year-plus-status filter returns.

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 a specific verb and resource ("List invoices") with the optional scoping dimensions named up front. It does not name list_recurring_invoices as a distinct sibling, but the resource word "invoices" is unambiguous enough to separate it from expense, contact, or report tools.

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 conveys that filtering by year or status is optional, which implies the call works unfiltered for a full listing, but it never states when an agent should reach for this versus list_recurring_invoices or export_books. Usage has to be inferred from the filter vocabulary rather than from explicit guidance.

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