buchpilot-mcp

get_overdue_invoices

List overdue invoices with amounts and due dates. Filter by minimum days overdue and limit results to streamline receivables management.

Instructions

Listet alle ueberfaelligen Rechnungen mit Betrag und Faelligkeitsdatum. Lists all overdue invoices with amount and due date.

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_overdue_invoices"
  }
}

Input Schema

Name	Required	Description
`days_overdue`	No	Mindestens X Tage ueberfaellig (0 = alle ueberfaelligen)
`limit`	No	Maximale Anzahl
`backend`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Apr 26, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided. The description only states what the tool does, not behavioral traits like read-only, auth requirements, or return format. Insufficient for an unannotated tool.

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?

Short and to the point, but bilingual repetition is redundant. Still efficient overall.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Lacks return structure details beyond amount and due date. No mention of sorting, pagination, or relationship to list_invoices. Incomplete for a filtered list tool with no annotations or output schema.

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 covers two of three parameters with descriptions (67% coverage). The description adds no parameter info. The 'backend' parameter is undocumented.

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 clearly states the tool lists overdue invoices with amount and due date, which distinguishes it from list_invoices (all invoices) and get_invoice (single). However, it doesn't explicitly differentiate from sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives like list_invoices. No prerequisites or exclusions mentioned.

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

Deploy Server