Skip to main content
Glama

Claimondo — Kfz-Gutachter finden & Termin buchen

by de.claimondo

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

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description reinforces this with 'Read-only und anonym' and adds behavioral details like returning a distance-sorted list, map image URL, and callback phone number. It does not contradict annotations. A minor gap is no mention of rate limits or auth, but given the tool's nature, this is acceptable.

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-structured with clear sections: purpose, read-only note, args, returns, usage. It is concise without being overly terse; every sentence adds value. Could be slightly more streamlined, but overall effective.

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?

Given the tool has 4 parameters and an output schema, the description provides a complete overview: what it does, inputs, output structure, and when to use. It lacks error handling details, but as a finder tool this is sufficient. The output schema is explicitly described in the 'Returns' section.

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 all parameters. The description's 'Args' section repeats most schema descriptions and adds examples (e.g., '50670'). It clarifies that PLZ OR ort must be provided, which is a slight addition. Baseline 3 is appropriate.

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 title and description clearly state it finds certified Kfz experts near a German postal code. The verb 'finde' and resource 'Sachverstaendige' are specific, and the description distinguishes from siblings like 'finde_gutachter_termine' (which finds appointment slots) and 'melde_schaden' (report damage).

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?

Explicit 'Use when' and 'Nicht für' sections provide clear guidance on when to use this tool (user asks for a car expert) and when not to (reporting damage, booking appointments). This helps the agent select the right tool among siblings.

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