Skip to main content
Glama

Adresse speichern

address_upsert
Destructive

Legt eine Adresse im Partner-Adressbuch an oder aktualisiert sie. Validiert die Adresse anhand landesspezifischer Regeln. EN: Creates or updates an address in the partner address book. Validates the address using country-specific rules.

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": {
      "name": "<name>",
      "street": "<street>",
      "city": "<city>"
    },
    "name": "address_upsert"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNo
cityYes
nameYes
poboxNo
streetYes
companyNo
countryNoISO-3166-alpha-2, default DE. EN: ISO 3166-1 alpha-2, defaults to DE.
addressIdNo
isDefaultNo
addressTypeNo
houseNumberNo
mandantennummerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

While annotations declare the operation is destructive, the description adds crucial behavioral context: that the address is validated using landesspezifische (country-specific) rules. This explains *how* the upsert operation behaves during input processing.

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 description is highly concise, and the core function of the tool (upsert and validation) is stated in the opening phrase, front-loading the necessary information efficiently.

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

Completeness2/5

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

Given the high parameter count (12) and the extremely low schema description coverage (8%), the description is dangerously vague. It does not provide enough context for an agent to confidently utilize the complex inputs available in the schema.

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

Parameters2/5

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

With 12 parameters and only 8% schema description coverage, the description is insufficient. It does not explain the business meaning of crucial fields like 'mandantennummer,' 'isDefault,' or 'addressType,' failing to add meaningful context beyond the basic operation.

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?

The description clearly identifies the primary action (create or update, i.e., upsert) and the resource (address in the partner address book). This distinguishes it functionally from sibling tools like address_list or address_search_company.

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?

It provides one specific guideline: the validation is performed using country-specific rules. However, it lacks guidance on the workflow—for example, whether the agent should call address_validate before this function, or if this function handles validation implicitly.

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.