Claimondo — Kfz-Gutachter finden & Termin buchen

Schaden melden + Gutachter-Termin anstoßen (WRITE)

claimondo_melde_schaden

Meldet einen Kfz-Schaden bei Claimondo und stößt die Gutachter-/Termin-Buchung an. ERZEUGT EINEN LEAD und sendet dem Kunden seinen persönlichen FlowLink per WhatsApp — eine SCHREIBENDE Aktion, kein read.

WICHTIG — Einwilligung (DSGVO): Rufe dieses Tool NUR mit einwilligung_erteilt=true auf, NACHDEM du dem Nutzer erklärt hast, dass (a) Claimondo seine Angaben zur Gutachter-/Termin-Vermittlung verarbeitet, (b) der Kontakt per WhatsApp erfolgt, (c) die Verarbeitung teils über einen KI-Dienst in den USA läuft — UND der Nutzer ausdrücklich zugestimmt hat. Ohne Zustimmung lehnt der Server ab (einwilligung_erforderlich).

WICHTIG — keine Rechtsberatung: Du vermittelst Gutachter + Termin (allgemeine Infos zur Schadensregulierung sind ok), keine individuelle Rechtsberatung.

Ablauf: erst claimondo_finde_gutachter_termine (Gutachter + freie Slots) → Nutzer wählt (sv_id + wunschtermin) → Name + WhatsApp-Nr erfragen → Einwilligung einholen → dieses Tool. Den finalen Termin + die Details (Vollmacht, Schuldfrage) setzt der Kunde anschließend selbst im FlowLink (/flow).

Returns: { ok, status, kanal (whatsapp|sms|email|none), hinweis }. KEIN Link/keine PII im Ergebnis — der Link geht direkt per WhatsApp an den Kunden.

Input Schema

TableJSON Schema

Name	Required	Description
`plz`	Yes	5-stellige PLZ des Besichtigungsorts (wo das Fahrzeug steht).
`name`	Yes	Name des Kunden.
`sv_id`	No	Opakes Gutachter-Handle aus claimondo_finde_gutachter_termine (gutachter[].id), falls gewählt.
`hergang`	Yes	Kurze Schilderung, was passiert ist (Unfallhergang).
`telefon`	Yes	WhatsApp-Nummer des Kunden (für den FlowLink-Versand).
`slot_end`	No	Gewählter Slot-ENDE als ISO-8601 (gutachter[].termine[].end). Zusammen mit slot_start.
`schadenart`	Yes	Schadenart / Unfalltyp, z. B. "Auffahrunfall", "Parkschaden".
`slot_start`	No	Gewählter Slot-START als ISO-8601 (gutachter[].termine[].start). Mit slot_end + sv_id → echte Termin-Reservierung.
`wunschtermin`	No	Optional: vager Wunschtermin (weicher Hold), falls KEIN konkreter Slot gewählt wurde.
`einwilligung_erteilt`	Yes	MUSS true sein und NUR nach ausdrücklicher Nutzer-Zustimmung gesetzt werden: Verarbeitung der Angaben + WhatsApp-Kontakt + Hinweis auf KI-Dienst/USA.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`kanal`	Yes
`status`	Yes
`hinweis`	Yes

TDQS

A4.8/5.0

Behavior5/5

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

Discloses key behaviors beyond annotations: it's a write action ('ERZEUGT EINEN LEAD'), sends WhatsApp, requires consent, and returns no link/PII. Annotations already indicate non-readOnly, and description adds critical context about side effects and data handling.

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?

Well-structured with bold headings and warnings, but somewhat verbose. Every sentence adds value, though some repetition (e.g., consent explanation). Front-loaded with purpose and warnings, then flow and return values.

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 complexity (10 params, 6 required, output schema exists), description covers prerequisites, workflow, behavior, and return format. It explicitly states what the output contains and what it does not contain, making it complete for an AI agent.

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% so baseline is 3. Description adds value by explaining the purpose of slot parameters and the consent parameter in the context of the workflow. It clarifies the relationship between sv_id, slot_start, slot_end, and wunschtermin, which aids correct usage.

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?

Description clearly states the primary action ('Meldet einen Kfz-Schaden und stößt die Gutachter-/Termin-Buchung an') and distinguishes from siblings by outlining the prerequisite step (claimondo_finde_gutachter_termine) and the resulting action (sending FlowLink). It uses specific verbs and resources.

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?

Provides explicit when-to-use guidance: after finding surveyor and obtaining consent. Warns about what not to do (no legal advice). Includes step-by-step workflow and explicitly mentions conditions for calling the tool (einwilligung_erteilt must be true).

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 tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool maps to a distinct stage of the customer journey: researching appraisers, searching workshops, decoding insurer letters, assessing claims, registering a case, requesting a callback, or checking case status. The only near-overlap—finde_gutachter_termine versus finde_sachverstaendige—is actively clarified within the descriptions, so an agent can confidently disambiguate.

Naming Consistency4/5

All tools share the claimondo_ prefix and use snake_case, which makes the set feel consistent. However, most tools follow a verb_object pattern (decode, finde, melde, pruefe, rueckruf), while fall_status is a noun phrase and rueckruf is a noun, creating a minor stylistic deviation.

Tool Count5/5

With 8 tools, the server is well-scoped for its purpose: searching, assessing, creating leads, and retrieving status. Each tool covers a meaningful part of the claims funnel without redundancy or bloat.

Completeness4/5

The tool set covers the main flow from finding an appraiser or workshop, to assessing claim rights, to creating a lead via claim submission or callback, and later checking status. There is no dedicated tool for rescheduling or cancelling a booked appointment, but that part is intentionally handled outside the MCP via the customer's FlowLink, so the core domain surface is solid.

Resources

Need Help?