Skip to main content
Glama

Produkt ändern

update_product
DestructiveIdempotent

Change a saved product of the connected facturo account by its product_id from list_products, e.g. 'der Stundensatz ist jetzt 95 Euro'. Pass ONLY the fields the user asked to change; omitted fields stay, an empty string clears description or vat_rate. Read the change back to the user (old and new value) and wait for their OK first. Documents already created keep their prices; items you add from now on take the new values.

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": {
      "product_id": "<product_id>"
    },
    "name": "update_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName as it goes onto the invoice line, one line, e.g. 'Regiestunde' or 'Fliesen verlegen'
unitNoUnit the price is for, e.g. 'Std', 'Stk', 'm²', 'pauschal'
priceNoUnit price in EUR as it goes onto the invoice line, e.g. '95', '95.50' or '95,50'
vat_rateNoOptional own VAT rate in percent ('10', '13', '4,9'), only on accounts with per-line VAT rates. Empty string: the product follows the document's rate.
product_idYes
descriptionNoOptional standard specs (dimensions, scope, options). They prefill the item details whenever the product goes onto a line.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: omitted fields stay (partial-update semantics), an empty string clears description or vat_rate, and existing documents keep their prices while newly added items take the new values. These side-effect disclosures are exactly what an agent needs for a destructive mutation.

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?

Front-loaded with the core action and identifier source, then the field-selection rule, then the confirmation workflow and side effects. Dense but every sentence carries information; slightly long for a single tool.

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

Completeness5/5

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

For a destructive, idempotent mutation with no output schema, the description covers partial updates, field clearing, downstream effects on existing documents, and the confirmation step. Nothing an agent needs in order to call it safely is missing.

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

Parameters4/5

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

Schema coverage is already 83%, so the baseline is 3; the description adds real meaning by explaining the empty-string clearing behavior and the partial-update contract. Minor tension with the schema's vat_rate wording ('follows the document's rate' vs 'clears') keeps it from a 5.

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?

States a specific verb and resource ('Change a saved product'), names the identifier source ('product_id from list_products'), and gives a concrete example of the change. An agent can distinguish this from create_product without opening either schema.

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?

Explicitly instructs to pass ONLY the fields the user asked to change and to read the change back and wait for confirmation before applying. It does not name an alternative tool or state when-not to use it, but the procedural guidance is unusually strong.

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