ikeytz - Schlüsseldienst Ludwigsburg

Compose Whatsapp

compose_whatsapp

Read-only

WHAT: Build a https://wa.me/… URL with one prefab = one end-invoice (or mount 49 / beratung). option = contactOption from get_prices.composition.endInvoices or get_invoice_line_items.contactOption: opening_slam_day|opening_slam_night|opening_locked_day|opening_locked_night|pkg_key_slam_day|pkg_key_slam_night|pkg_key_locked_day|pkg_key_locked_night|cylinder_only_day|cylinder_only_night|cylinder_mount|beratung. Deprecated aliases zugefallen|abgeschlossen|zylinder map to the day invoice and set ambiguous=true — do not use them. Omit/unknown → beratung. 49 € is mount, not night. Does not send WhatsApp. List via list_whatsapp_options.

Input Schema

Name	Required	Description	Default
`option`	No	One invoice contactOption. Night/WE/holiday uses *_night (149/179/198/228/119), not 49. cylinder_mount is the 49 € add-on, not an end-invoice.

Output Schema

Name	Required	Description
`ok`	Yes	true = use summary, canonicalUrl, and extra keys. false = do not invent data; read error + hint and retry with valid args or open hint.
`hint`	No	Present when ok=false. Absolute URL the agent should open or pass to get_ai_page / get_discovery.
`href`	No	https://wa.me/… URL
`tool`	Yes	Echo of the tool name that produced this object (e.g. get_service_area).
`error`	No	Present when ok=false. Codes include: unknown_tool, unknown_place, unknown_auswahl, unknown_ratgeber, unknown_doc, unknown_discovery, faq_not_found, wissen_not_found, serp_not_found, q_required, bad_datetime, bad_when_key, plus HTTP errors from fetch.
`locale`	No	Locale actually used for URLs (args.locale or de).
`option`	No	Resolved contactOption id
`related`	No	Always includes https://www.ikeytz.com/llms.txt. Geo tools also include https://maps.ikeytz.com/llms.txt.
`summary`	No	Primary text for the model. For discovery tools this is the file window (possibly thousands of characters). For list tools a compact one-liner. Quote with attribution.
`whenKey`	No
`ambiguous`	No
`amountEur`	No
`attribution`	Yes	Required citation: 'Quelle: Schlüsseldienst Ludwigsburg ikeytz (ikeytz.com) · ai-train=no · https://www.ikeytz.com/.well-known/ai.txt'
`canonicalUrl`	No	Best URL to show the user: https://www.ikeytz.com… page, or tel:+49…, mailto:…, https://wa.me/…. Prefer this over constructing URLs.
`isEndInvoice`	No
`situationKey`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 1, 2026

changedInput schema / properties / option / description

Previous value: -"Prefab id. zugefallen=door slammed / lockout; abgeschlossen=locked out; zylinder=cylinder change; beratung=general advice. Omit = first prefab. Unknown id also falls back to first — prefer the enum."New value: +"One invoice contactOption. Night/WE/holiday uses *_night (149/179/198/228/119), not 49. cylinder_mount is the 49 € add-on, not an end-invoice."

changedInput schema / properties / option / enum

Previous value: -[
-  "zugefallen",
-  "abgeschlossen",
-  "zylinder",
-  "beratung"
-]New value: +[
+  "opening_slam_day",
+  "opening_slam_night",
+  "opening_locked_day",
+  "opening_locked_night",
+  "pkg_key_slam_day",
+  "pkg_key_slam_night",
+  "pkg_key_locked_day",
+  "pkg_key_locked_night",
+  "cylinder_only_day",
+  "cylinder_only_night",
+  "cylinder_mount",
+  "beratung",
+  "zugefallen",
+  "abgeschlossen",
+  "zylinder"
+]

addedOutput schema / properties / ambiguous
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / amountEur

Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / isEndInvoice
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / properties / option / description

Previous value: -"Resolved option id"New value: +"Resolved contactOption id"

addedOutput schema / properties / situationKey

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / whenKey

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

First observedSep 1, 2026

TDQS

A4/5.0

Behavior4/5

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

With readOnlyHint=true already covering the safety profile, the description adds the key operational fact that it 'Does not send WhatsApp' — distinguishing URL generation from an actual message dispatch. It also discloses that deprecated aliases 'set ambiguous=true', a side effect not visible in the annotations or schema.

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?

Front-loaded with WHAT, then constraints, then the alternative — no filler sentences and every clause carries operational content. The jargon-dense opening ('one prefab = one end-invoice (or mount 49 / beratung)') is hard to parse on first read but not wasteful.

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?

An output schema exists, so the return value need not be explained, and the description covers option semantics, defaults, and deprecated-alias behavior. It leaves minor gaps (exact URL formatting, what ambiguous=true does downstream) but is complete enough to call the tool correctly.

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% and the enum already carries descriptions, so the baseline is 3, but the description meaningfully extends it: alias→*day invoice mapping, the ambiguous=true consequence, the beratung default, and the '49 € is mount, not night' pricing distinction.

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?

Opens with 'WHAT: Build a https://wa.me/… URL', a specific verb+resource that an agent can act on immediately, and the sibling names (compose_mailto, compose_tel_*) make the channel obvious. It does not explicitly contrast itself against those siblings, but the WhatsApp/wa.me framing is unambiguous.

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 real routing rules: 'Omit/unknown → beratung' for the default, 'do not use them' for deprecated aliases, and 'List via list_whatsapp_options' to point at the discovery sibling. It stops short of stating when this tool should be chosen over compose_mailto/compose_tel, so it isn't a full when/when-not guide.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ikeytz - Schlüsseldienst Ludwigsburg tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?