Skip to main content
Glama

Adresse prüfen

address_validate
Read-only

Prüft eine Adresse anhand landesspezifischer Regeln und liefert valid (dasselbe Urteil wie die Adressprüfung von order_send) sowie je Feld, was fehlt, falsch geformt ist oder vom Ort abweicht. Nur eine Prüfung, das Adressbuch bleibt unverändert; Anlegen und Ändern übernimmt address_upsert. EN: Validates an address using country-specific rules and returns valid (the same verdict as the order_send address check) plus, per field, what is missing, malformed or differs from the city. A check only, the address book is left untouched; address_upsert creates and changes addresses.

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_validate"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description reinforces this ('address book left untouched') and adds the meaningful behavioral detail that the verdict matches order_send's check, plus what the response reports per field. It does not mention rate limits, auth needs, or what happens with an openWorld lookup, so it stops short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The substance is front-loaded and the mutation-exclusion comes early, but the full German/English duplication roughly doubles the length without adding information. Efficient in content, wasteful in form.

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

Completeness3/5

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

With no output schema, the description usefully describes the return value (a valid flag plus per-field missing/malformed/mismatch reasons). However, for a 12-parameter tool with 8% schema coverage, the unexplained fields — especially isDefault and reasoning on a read-only call — leave real ambiguity about how to invoke it correctly.

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?

Schema coverage is only 8% across 12 parameters, so the description must compensate and largely does not. It hints at country-driven rules but never explains addressType, isDefault, reasoning, mandantennummer, or pobox — several of which look incongruous for a pure validation call and need clarification.

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 ('validates an address using country-specific rules') and explicitly contrasts itself with address_upsert ('creates and changes addresses'). An agent can distinguish it from address_upsert and address_search_company 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?

Gives a clear when-not ('a check only, the address book is left untouched') and names the alternative for mutations (address_upsert). It also signals parity with the order_send address check, which helps an agent decide to pre-validate before sending. It does not discuss validation vs. sender_profile_validate, but that is a different resource.

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.