Skip to main content
Glama

Kunde ändern

update_client
DestructiveIdempotent

Change fields of a client of the connected facturo account. Pass ONLY the fields the user asked to change; omitted fields stay untouched, an empty string clears a field (not client_name or country). Read the change back to the user (old and new value) and wait for their OK first. A new UID is checked against VIES before it is saved. Documents already created keep the client data they were created with.

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": {
      "client_id": "<client_id>"
    },
    "name": "update_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidNoEU VAT number, e.g. ATU12345678
zipNoPostal code
cityNoCity
emailNoEmail the documents go to
phoneNoPhone number
streetNoStreet and house number
countryNoTwo-letter country code (AT, DE, CH, IT ...), default AT
client_idYes
name_line2NoSecond address line (contact person, department, c/o)
client_nameNoCompany or person name as printed on documents
mobile_phoneNoMobile number
payment_termsNoPayment terms printed for this client, e.g. 'Zahlbar innerhalb von 14 Tagen'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true, idempotentHint=true) by disclosing partial-update semantics, the clearing convention and its exceptions, a VIES validation step for new UIDs, and the important side effect that already-created documents retain their original client data.

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?

Four tight sentences, front-loaded with the core action, then update semantics, then the confirmation workflow, then side effects. No filler and nothing repeated from the schema.

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 12-parameter mutation tool with no output schema, the description covers update semantics, validation, confirmation, and downstream effects on documents. Only error/failure behavior (e.g. what happens if VIES rejects the UID) is left unstated.

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 92%, so the baseline is 3; the description adds real meaning on top by explaining the empty-string clearing rule and its two exceptions, plus the VIES check applied to the uid field.

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

Purpose4/5

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

States a specific verb and resource: 'Change fields of a client of the connected facturo account.' The partial-update framing ('Pass ONLY the fields the user asked to change') makes it clearly distinct from create_client, though no sibling is named explicitly.

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?

Gives concrete when/how guidance: pass only requested fields, omitted fields stay untouched, empty string clears a field except client_name/country, and confirm old vs new value with the user before saving. It does not name an alternative tool for full replacement or creation, which keeps it just short of a 5.

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