Skip to main content
Glama

Claimondo — Kfz-Gutachter finden & Termin buchen

by de.claimondo

Buchbare Kfz-Gutachter + freie Termine finden

claimondo_finde_gutachter_termine
Read-onlyIdempotent

Findet buchbare Partner-Kfz-Gutachter MIT freien Terminen im Umkreis einer deutschen Postleitzahl über Claimondo.

Anders als claimondo_finde_sachverstaendige (nur anonymisierte Liste) liefert dieses Tool die buchbaren Gutachter mit konkreten freien Slots (Vorschau aufs Buchen). Read-only und anonym — legt nichts an und meldet keinen Schaden.

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".

  • wunschtermin (string, optional): Wunschtermin als ISO-8601 (steuert das Slot-Ranking, kein harter Filter).

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

Returns (structuredContent bzw. json): { plz, ort, standort, wunschtermin, anzahl_gutachter, gutachter: [{ id, vorname, profilbild, bewertung_schnitt, bewertung_anzahl, entfernung, ist_top_partner, wunschtermin_frei, termine: [{ start, end, passung }], buchungs_url }], interaktive_karte_url, buchungs_telefon }

Use when: Nutzer will einen Gutachter-Termin sehen/vergleichen (z. B. „wann hat ein Gutachter in 50670 Zeit?").

WICHTIG beim Empfehlen eines Gutachters: Geben Sie dessen gutachter[].buchungs_url als Link aus. Er öffnet den Finder mit genau diesem Gutachter vorausgewählt; der Kunde ergänzt nur noch Adresse und Kontakt und bestätigt selbst. Verlinken Sie NICHT interaktive_karte_url, wenn Sie einen konkreten Gutachter genannt haben — das ist die allgemeine Karte ohne Auswahl und schickt den Kunden zurück an den Anfang der Suche. Die Karte ist nur richtig für „zeig mir alle in der Nähe". Hinweis: gutachter[].id + ein termin.start sind zusätzlich das Buchungs-Handle für claimondo_melde_schaden (mit Einwilligung); telefonisch geht es über buchungs_telefon. Fehlt buchungs_url (ältere API-Version), bleibt die Karte der Weg.

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.
wunschterminNoOptionaler Wunschtermin als ISO-8601-Zeitstempel (z. B. 2026-06-20T10:00:00Z) — steuert das Slot-Ranking, kein harter Filter.
response_formatNoAusgabeformat: 'markdown' (menschenlesbar) oder 'json' (strukturiert).markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ortYes
plzYes
standortYes
gutachterYes
wunschterminYes
anzahl_gutachterYes
buchungs_telefonYes
interaktive_karte_urlYes

TDQS

A4.7/5.0
Behavior5/5

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

The description states it is read-only and anonymous, and explicitly says 'legt nichts an und meldet keinen Schaden', which adds a behavioral dimension beyond the raw annotations. It also reveals key nuances: wunschtermin only influences slot ranking rather than acting as a hard filter, and an older API version may lack buchungs_url with the map as fallback path. These are non-obvious behavioral facts an agent needs to know.

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

Conciseness5/5

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

Though the description is longer than average, it earns its length: sections are organized with headings/paragraphs, front-loaded with purpose and sibling contrast, and every paragraph adds either selection guidance, response-shape context, or critical link behavior that is absent from the structured data. The 'WICHTIG' and 'Hinweis' blocks are particularly high-value operational guidance.

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?

The description includes the full output/return shape, explains the ranking-affecting nature of wunschtermin, gives a practical when-to-use example, and documents two URL-ownership situations that could easily cause user-facing errors. It even states how the tool relates to claimondo_melde_schaden via gutachter[].id plus termin.start. For a 4-parameter search tool, this is complete and decision-relevant.

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 baseline is 3. The Args section largely restates the schema definitions (format, required-alternative relation between plz and ort, wunschtermin semantics, response_format). It does not add meaningfully new parameter semantics beyond what the schema already documents. The optional-plz/ort interplay is mentioned in both the schema and the description, but there is no extra contract detail.

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 opens with a specific verb and resource: 'Findet buchbare Partner-Kfz-Gutachter MIT freien Terminen im Umkreis einer deutschen Postleitzahl'. It explicitly distinguishes itself from the sibling claimondo_finde_sachverstaendige, which returns only an anonymized list. An agent can immediately tell what this tool does and how it differs from its nearest alternative.

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?

The description gives clear when-to-use guidance: 'Nutzer will einen Gutachter-Termin sehen/vergleichen'. It also names the sibling alternative and the condition that selects it — claimondo_finde_sachverstaendige for an anonymized list, this tool for bookable experts with concrete free slots. Additional practical guidance (link buchungs_url, do not link interaktive_karte_url when recommending one expert, use the map only for 'show all nearby') further clarifies correct usage.

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