buchpilot-mcp

get_invoice

Retrieve a specific invoice by providing its ID. Access invoice details directly for accounting and management tasks in German-speaking business automation.

Instructions

Ruft eine Rechnung per ID ab. Gets an invoice by ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_invoice"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Rechnungs-ID
`backend`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Apr 26, 2026

TDQS

C2.8/5.0

Behavior1/5

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

No annotations are provided, so the description carries the full burden. It does not disclose any behavioral traits such as required permissions, error conditions, rate limits, or whether the operation is purely read-only. The description only states the basic function.

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?

The description is very short and avoids unnecessary words. However, it redundantly states the same information in two languages. It could be more concise by keeping one language and more structured by adding relevant details.

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?

Given the absence of annotations and output schema, the description should provide more context about what the tool returns, error handling, and parameter details. It only covers the basic purpose, leaving out critical information for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50% (only 'id' has a description). The description does not add any meaning beyond the schema, particularly for the 'backend' parameter which lacks a schema description. The tool description fails to compensate for the missing parameter documentation.

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 clearly states the tool retrieves an invoice by its ID. It uses a specific verb ('get' / 'abrufen') and resource ('invoice'), and it distinguishes itself from sibling tools like create_invoice, list_invoices, and update_invoice.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., list_invoices for searching, get_invoice_pdf for PDF retrieval). There are no prerequisites or usage conditions mentioned.

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

Deploy Server