Skip to main content
Glama

Letzte Rechnungen

get_recent_invoices
Read-onlyIdempotent

List the newest invoices of the connected facturo account with status (open, overdue, paid, cancelled with the Storno in cancelled_by, issued for a Storno or Gutschrift), totals, items, VAT mode, PDF links and when they were last emailed. Filter by client, text or status. Use it to answer 'what did I bill Huber' or 'what is still open', and to copy an earlier invoice ('the same as last time'): take items, vat_exemption_type, vat_rate, prices_include_vat and the discount fields from the row. The PDF links are for the user to open.

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

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 10
searchNoMatches invoice number, client name, reference lines or an item description
statusNo'open' means not yet due
client_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: how cancellations are represented (Storno in cancelled_by), that the response is capped at the newest rows, and the operational warning that PDF links are for the user to open rather than to be fetched.

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?

It is a single dense paragraph, but it is correctly front-loaded: what is returned first, then how to filter, then what questions it answers. The copy-an-earlier-invoice sentence is long but carries concrete field names that earn their space; only the parenthetical status list drifts into ambiguity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 must carry the return shape, and it does enumerate the returned fields comprehensively. Ordering ('newest') and the row cap are stated, and the copy-forward recipe covers the main non-obvious downstream action, so an agent has what it needs to call and use the result.

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 75% and the schema already documents limit, search, and status semantics ('open' means not yet due). The description restates the filter dimensions as 'client, text or status' but does not clarify client_id (the one undocumented parameter), the limit cap, or the fact that 'cancelled' is a returned value and not a valid status filter, which the status list in the description could imply.

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 opens with a specific verb and resource ('List the newest invoices of the connected facturo account') and enumerates exactly what each row carries: status, totals, items, VAT mode, PDF links, and last-emailed time. That is far more than a restatement of the name and is enough to distinguish it from siblings like import_invoices, finalize_invoice, or get_recent_offers.

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 concrete triggering questions ('what did I bill Huber', 'what is still open') and a second distinct use case, copying an earlier invoice, plus the exact fields to carry over. It stops short of naming when NOT to use it or pointing to a specific alternative tool for other queries, so it is clear context without exclusions.

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