Skip to main content
Glama

MaxRechnung

Änderungshistorie (GoBD)

get_invoice_audit
Read-only

Tarif: in jedem Tarif (Free, Pro, Business).

Änderungshistorie (GoBD)

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

Input Schema

NameRequiredDescriptionDefault
idYesInterne `id` der Rechnung (UUID), nicht die Belegnummer. Zu einer Nummer (z. B. `RE-2026-0004`) liefert `GET /invoices?number=…` (MCP: `list_invoices` mit `number`) die `id`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — no statement that the history is append-only/immutable (the GoBD implication), what entries contain, or whether history is retained after cancellation/deletion. The only added sentence is a pricing note, which is not behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short with no filler prose, but the front-loaded sentence is the least useful information (plan availability) and the actual purpose appears only as a bare title fragment. Structure is inefficient in ordering rather than in length.

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?

With no output schema, the description carries the burden of explaining what an audit-history response looks like (entry list, timestamps, changed fields, actor). None of that is present, so an agent knows neither the return shape nor the compliance purpose behind the call.

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 description coverage is 100% and the single `id` parameter is documented thoroughly, including how to resolve a Belegnummer to an id via list_invoices. The description contributes nothing to parameter meaning; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description consists of a plan-availability line plus the noun phrase "Änderungshistorie (GoBD)", which merely restates the title. It never states a verb or says explicitly that it returns the change/audit history of a single invoice, nor how that differs from get_invoice or get_invoice_summary.

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?

"Tarif: in jedem Tarif (Free, Pro, Business)" only informs about plan gating and adds no when-to-use guidance. There is no indication of when an agent should fetch the audit trail instead of the invoice itself, and no mention of the GoBD retention purpose as a usage trigger.

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