Skip to main content
Glama

Kunde anlegen

create_client
Idempotent

Save a new client of the connected facturo account. Only after search_clients found no match. Fill every field you know; ask the user for the address if it is missing (documents need it). A client with the same name (and street) already exists is returned instead of duplicated. For a client that only appears on one invoice, preview_invoice with a client object does this on its own.

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_name": "<client_name>"
    },
    "name": "create_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
name_line2NoSecond address line (contact person, department, c/o)
client_nameYesCompany 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.5/5.0
Behavior4/5

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

Goes beyond the annotations by explaining the dedup rule concretely: an existing client with the same name and street is returned instead of creating a duplicate, which gives real meaning to idempotentHint=true. It also flags the document-address dependency, but says nothing about what happens on failure or invalid VAT input.

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?

Four short sentences, front-loaded with purpose then rules, no filler. The dedup sentence is grammatically awkward ('A client with the same name (and street) already exists is returned'), which slightly hurts scannability but not comprehension.

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 an 11-parameter mutation with only one required field and no output schema, the description covers purpose, preconditions, dedup result, and the alternative path. The only real gap is return-value detail beyond the dedup case, which is minor given how fully the schema documents inputs.

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 100%, so baseline is 3; the description earns an extra point by giving operational intent for the fields ('Fill every field you know') and explaining why address fields matter (documents need them). It does not restate individual field formats, which is appropriate since the schema already does.

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 ('Save a new client of the connected facturo account') and immediately distinguishes itself from search_clients and preview_invoice. An agent can tell what this creates and which sibling covers the case it does not.

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 precondition ('Only after search_clients found no match') and names the alternative for the edge case ('For a client that only appears on one invoice, preview_invoice with a client object does this on its own'). When-to-use and when-not-to-use are both covered.

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