Skip to main content
Glama

MaxRechnung

Entwurf bearbeiten

update_invoice_draft

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

Entwurf bearbeiten

Ändert Felder an einem Entwurf. Festgeschriebene Belege lehnen das mit 409 ab – außer der Body enthält nur custom_fields (eigene Felder gehören nicht zum Beleg). Scope invoices:draft (oder invoices:write). Statuswechsel (Festschreiben, Bezahlt-Markieren): PATCH /invoices/{id}/status.

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

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`.
bodyNoJSON-Request-Body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations, it discloses plan availability, required scope (`invoices:draft` or `invoices:write`), the `409` behavior for finalized invoices, and the `custom_fields`-only exception. It does not describe return behavior or partial-update semantics, but the main mutation constraints are covered.

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?

The content is mostly relevant, but it repeats the title "Entwurf bearbeiten" and places tariff information before the actual purpose. The core mutation description is compact, but these redundancies keep it from being fully front-loaded.

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 complex mutation with a large nested body, the description covers the important behavioral constraints and scope while the schema documents the individual fields. Minor gaps remain around partial-update behavior and response details, but nothing essential for correct selection is missing.

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%, so the schema already carries detailed parameter meaning. The description adds some semantic context around `custom_fields` and status changes, but does not meaningfully enrich the many other body fields beyond the schema.

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 uses a specific verb and resource: "Ändert Felder an einem Entwurf" (changes fields on a draft). It also distinguishes status changes by pointing to `PATCH /invoices/{id}/status`, so an agent can tell this apart from status-update siblings.

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 clear usage boundaries: finalized invoices reject the call with `409` unless the body contains only `custom_fields`, and status changes belong to a separate endpoint. It does not explicitly name the MCP sibling `update_invoice_status`, but the alternative is still clear.

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