Skip to main content
Glama

Firmendaten ändern

update_profile
DestructiveIdempotent

Change the company profile of the connected facturo account PERMANENTLY: sender address, UID, Firmenbuch data, default Zahlungsziel, document defaults (Kleinunternehmer, Honorarnote, EPC QR code), standard texts and the numbering start. Only for 'from now on' wishes; a one-off text or VAT mode for a single document goes into preview_invoice/preview_offer instead. Pass ONLY the fields the user asked to change; omitted fields stay, an empty string clears a text. Read the change back and wait for the user's OK first. Bank data and the logo are changed at facturo.at.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidNoOwn UID (ATU...), needed for reverse charge and EU documents; checked against VIES
zipNoPostal code
cityNoCity
dgnrNoDienstgebernummer
emailNoContact email printed on documents
phoneNoContact phone printed on documents
streetNoStreet and house number
fusstextNoStandard text below the totals on invoices
kopftextNoStandard text above the items on invoices
kv_fusstextNoStandard text below the totals on Kostenvoranschläge
kv_kopftextNoStandard text above the items on Kostenvoranschläge
company_nameNoCompany name as printed on documents
offer_fusstextNoStandard text below the totals on Angebote
offer_kopftextNoStandard text above the items on Angebote
firmenbuchnummerNoFirmenbuch number (FN ...)
show_epc_qr_codeNoPrint the EPC payment QR code on invoices. Part of the paid plans, switching it on fails on a free plan.
firmenbuchgerichtNoFirmenbuch court
next_offer_numberNoThe number the next Angebot/KV/AB gets this year. Can only move up past the numbers already issued this year.
next_invoice_numberNoThe number the next invoice gets this year. Can only move up past the numbers already issued this year.
prefers_honorarnoteNoNew invoices are Honorarnoten by default (freelancers, doctors)
default_payment_daysNoDefault Zahlungsziel in days for new invoices
email_default_text_offerNoDefault email body when sending Angebote
email_default_text_invoiceNoDefault email body when sending invoices
kleinunternehmer_default_enabledNoKleinunternehmer: new documents show no USt by default (§ 6 Abs 1 Z 27 UStG)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only flag destructive=true and idempotent=true; the description adds the operationally important traits: changes are PERMANENT, omitted fields are preserved, an empty string clears text, and numbering fields can only move up past already-issued numbers. The read-back-and-confirm instruction goes well beyond what the annotation set conveys.

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?

The critical constraint (PERMANENT) and the alternative-route guidance are front-loaded, and every sentence carries information — permanence, alternatives, patch semantics, confirmation workflow, out-of-scope fields. It is a single dense run-on block without paragraph breaks or bullets, which slightly hurts scannability for a 24-parameter tool, but there is no filler.

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 24-parameter mutation with no output schema, the definition covers what annotations cannot: partial-update semantics, clearing semantics, permanence, numbering constraints, plan gating on the EPC QR flag, user-confirmation workflow, and which fields must be changed elsewhere. An agent has everything needed to invoke it safely without guessing.

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 100%, so per-field meaning is already documented. The description still adds genuine semantics the schema lacks as a whole: partial-update behavior ("Pass ONLY the fields the user asked to change; omitted fields stay") and the empty-string clearing convention, which an agent could not infer from 24 individually-described properties. No syntax/format detail is added for the typing fields (UID, Firmenbuchnummer), hence not 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+resource ("Change the company profile of the connected facturo account") and enumerates the concrete domains affected: sender address, UID, Firmenbuch data, default Zahlungsziel, document defaults, standard texts, numbering start. It also names the sibling tools it is not (preview_invoice/preview_offer) and the out-of-scope items handled elsewhere (bank data, logo at facturo.at), so an agent can separate it from get_profile and the preview tools without opening schemas.

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

Usage Guidelines5/5

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

Gives an explicit decision rule: "Only for 'from now on' wishes; a one-off text or VAT mode for a single document goes into preview_invoice/preview_offer instead." It also routes bank data and logo changes to facturo.at, and adds a procedural precondition ("Read the change back and wait for the user's OK first"). When-to-use, when-not-to-use, and alternatives are all present.

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