Skip to main content
Glama
berthelius

Frihet MCP Server

Update Invoice

update_invoice
Idempotent

Update an existing invoice by sending only the fields to change. For example, mark an invoice as paid by providing its ID and status.

Instructions

Update an existing invoice using PATCH semantics. Only the provided fields will be changed. Example: id='abc123', status='paid' to mark an invoice as paid. / Actualiza una factura existente. Solo se modifican los campos proporcionados.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesInvoice ID / ID de la factura
itemsNoLine items / Conceptos
notesNoNotes / Notas
statusNoInvoice status / Estado
dueDateNoDue date (YYYY-MM-DD) / Fecha de vencimiento
taxRateNoTax rate % / IVA %
clientIdNoExisting client ID — server back-fills taxId/address / ID de cliente existente
irpfRateNoIRPF withholding % (retencion autonomo ES, e.g. 15 or 7) / Retencion IRPF %
poNumberNoClient purchase-order reference / Numero de pedido del cliente
seriesIdNoInvoice numbering series ID / ID de serie de numeracion
issueDateNoIssue date (YYYY-MM-DD) / Fecha de emision
clientNameNoClient name / Nombre del cliente
prepaymentNoPrepaid/advance amount already collected in EUR / Anticipo cobrado en EUR
clientTaxIdNoClient tax ID (NIF/CIF/VAT) shown on the invoice / NIF/CIF del cliente
discountRateNoGlobal discount % applied to the invoice / Descuento global %
clientAddressNoClient billing address shown on the invoice / Direccion fiscal del cliente
operationTypeNoOperation type (service or goods) / Tipo de operacion
clientLocationNoFiscal zone driving IVA vs IGIC vs exempt / Zona fiscal (IVA/IGIC/exento)
documentNumberNoExternally-issued number for import (honored verbatim) / Numero externo para importacion
equivalenceSurchargeRateNoRecargo de equivalencia % (ES retail regime) / Recargo de equivalencia %

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
itemsNo
notesNo
totalNo
statusNo
dueDateNo
taxRateNo
createdAtNo
issueDateNo
updatedAtNo
clientNameNo
Behavior3/5

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

Annotations already provide readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds that it uses PATCH semantics and only modifies provided fields, which aligns with idempotentHint but does not go beyond annotations significantly.

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

Conciseness5/5

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

The description is very concise with two sentences, a helpful example, and a Spanish translation. All information is front-loaded, with no wasted words.

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 tool with 20 parameters and an output schema, the description covers core behavior (PATCH, partial update) and provides an illustrative example. It could mention prerequisites like invoice existence or valid status transitions, but overall it is sufficient for agent decision-making.

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 each parameter is well-documented in the schema. The description only mentions 'id' and 'status' in an example, adding minimal extra value 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 clearly states the verb 'Update' and the resource 'invoice', specifying PATCH semantics and partial updates, which distinguishes it from create, delete, duplicate, and other invoice-related tools.

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

Usage Guidelines3/5

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

The description implies usage for modifying existing invoices but does not explicitly state when to use this tool over siblings like 'mark_invoice_paid' or 'create_invoice'. No exclusion criteria or alternative suggestions are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/berthelius/frihet-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server