Skip to main content
Glama

Claimondo — Kfz-Gutachter finden & Termin buchen

by de.claimondo
OverviewDiscussionsAdmin

Kfz-Sachverständige in der Nähe finden

claimondo_finde_sachverstaendige
Read-onlyIdempotent

Findet zertifizierte Partner-Kfz-Sachverständige im Umkreis einer deutschen Postleitzahl über Claimondo (bundesweite Schadensregulierungs-Plattform).

Read-only und anonym — legt nichts an und meldet keinen Schaden. Liefert eine nach Entfernung sortierte, datenschutz-anonymisierte Trefferliste, eine Karten-Bild-URL (im Chat einbettbar), einen Link zur interaktiven Karte mit freien Terminen und eine Rückruf-Telefonnummer.

Args:

  • plz (string): 5-stellige deutsche PLZ, z. B. "50670". PLZ ODER ort angeben.

  • ort (string): Stadt/Adresse als Alternative zur PLZ, z. B. "Köln" oder "Berlin Mitte".

  • radius (number): Suchradius in km, 1-200 (Standard 30).

  • response_format ("markdown" | "json"): Ausgabeformat (Standard "markdown").

Returns (structuredContent bzw. json): { plz, ort, standort, radius_km, anzahl_treffer, sachverstaendige: [{ tier, stadt, entfernung_km, spezialisierungen, bewertung_schnitt, bewertung_anzahl }], karte_url, interaktive_karte_url, buchungs_telefon }

Use when: Nutzer fragt nach einem Kfz-Gutachter/Sachverständigen in einer Stadt oder Region (z. B. nach einem Unfall). Nicht für: Schaden melden, Termin buchen oder Rechtsberatung — das gibt es in dieser read-only-Stufe bewusst nicht.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ortNoStadt/Adresse als Alternative zur PLZ, z. B. "Köln" oder "Berlin Mitte". PLZ ODER ort angeben.
plzNo5-stellige deutsche Postleitzahl, z. B. 50670 für Köln. PLZ ODER ort angeben.
radiusNoSuchradius in Kilometern (1–200, Standard 30).
response_formatNoAusgabeformat: 'markdown' (menschenlesbar) oder 'json' (strukturiert).markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ortYes
plzYes
standortYes
karte_urlYes
radius_kmYes
anzahl_trefferYes
buchungs_telefonYes
sachverstaendigeYes
interaktive_karte_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / ort
      Added value: +{
+  "description": "Stadt/Adresse als Alternative zur PLZ, z. B. \"Köln\" oder \"Berlin Mitte\". PLZ ODER ort angeben.",
+  "maxLength": 120,
+  "minLength": 2,
+  "type": "string"
+}
    • changedInput schema / properties / plz / description
      Previous value: -"5-stellige deutsche Postleitzahl, z. B. 50670 für Köln."New value: +"5-stellige deutsche Postleitzahl, z. B. 50670 für Köln. PLZ ODER ort angeben."
    • removedInput schema / required
      Removed value: -[
-  "plz"
-]
    • addedOutput schema / properties / ort
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / standort
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "plz",
-  "radius_km",
-  "anzahl_treffer",
-  "sachverstaendige",
-  "karte_url",
-  "interaktive_karte_url",
-  "buchungs_telefon"
-]New value: +[
+  "plz",
+  "ort",
+  "standort",
+  "radius_km",
+  "anzahl_treffer",
+  "sachverstaendige",
+  "karte_url",
+  "interaktive_karte_url",
+  "buchungs_telefon"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, but the description goes well beyond them by stating that the call is anonymous, creates nothing, reports no damage, and returns a privacy-anonymized, distance-sorted result list plus embeddable maps and a callback number. This gives the agent a reliable mental model of the tool's side-effect-free behavior.

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 well organized and front-loaded: purpose, safety, then compact Args/Returns/Use-when sections. It earns a 4 rather than 5 because the Args and Returns sections substantially duplicate the input schema and output schema, but the structure remains scannable and useful for an agent.

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?

Given the complete input schema, clear annotations, and output schema, this description covers everything an agent needs: input options, defaults, output format selection, return structure, and routing conditions. It even adds non-obvious context such as the embeddable map image URL and callback phone number, making it fully usable in a chat-facing tool.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents plz, ort, radius, and response_format. The description's Args section largely restates the same constraints and the 'PLZ ODER ort' dependency is also already in the schema, so it adds little new semantic value beyond what structured data provides.

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?

The description states a specific verb ('Findet'), a specific resource ('zertifizierte Partner-Kfz-Sachverständige'), and a clear scope ('Umkreis einer deutschen Postleitzahl'). It also frames the tool as a read-only search rather than a damage-reporting or booking action, which helps distinguish it from the Claimondo siblings.

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?

The description provides explicit 'Use when' guidance ('Nutzer fragt nach einem Kfz-Gutachter...') and an explicit 'Nicht für' list that excludes Schaden melden, Termin buchen, and Rechtsberatung. However, it does not name sibling tools as alternatives, and mentioning 'freien Terminen' in the output could still create mild ambiguity against the sibling finde_gutachter_termine.

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

All Claimondo — Kfz-Gutachter finden & Termin buchen toolsInspect
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