Claimondo — Kfz-Sachverständigen-Finder
Server Details
Findet zertifizierte Kfz-Sachverständige im Umkreis einer deutschen PLZ — anonym, read-only.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.6/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion or overlap. The tool's purpose is clearly distinct from nothing else.
The single tool name follows a clear verb_noun pattern in German (finde_sachverstaendige), consistent with the server's theme.
One tool is at the low end of the acceptable range for a server. While the tool is functional, the surface feels thin and could benefit from additional related operations.
For its stated read-only purpose of finding certified experts, the tool provides all necessary outputs (list, map, contact info). There are no missing features given the scope.
Available Tools
1 toolclaimondo_finde_sachverstaendigeKfz-Sachverständige in der Nähe findenARead-onlyIdempotentInspect
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".
radius (number): Suchradius in km, 1-200 (Standard 30).
response_format ("markdown" | "json"): Ausgabeformat (Standard "markdown").
Returns (structuredContent bzw. json): { plz, 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.
| Name | Required | Description | Default |
|---|---|---|---|
| plz | Yes | 5-stellige deutsche Postleitzahl, z. B. 50670 für Köln. | |
| radius | No | Suchradius in Kilometern (1–200, Standard 30). | |
| response_format | No | Ausgabeformat: 'markdown' (menschenlesbar) oder 'json' (strukturiert). | markdown |
Output Schema
| Name | Required | Description |
|---|---|---|
| plz | Yes | |
| karte_url | Yes | |
| radius_km | Yes | |
| anzahl_treffer | Yes | |
| buchungs_telefon | Yes | |
| sachverstaendige | Yes | |
| interaktive_karte_url | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint and destructiveHint false. The description adds context beyond annotations: 'Read-only und anonym — legt nichts an und meldet keinen Schaden' and describes the output. No contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is well-structured with separate sections for main purpose, arguments, returns, and usage guidance. It is front-loaded. Slightly verbose but not excessive.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity, schema coverage, and output schema presence, the description is complete. It covers purpose, parameters, behavioral traits, return structure, and usage boundaries.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so description adds limited new info. It repeats schema details (zip code example, radius range, format enum) but in a more conversational form. No additional semantics beyond schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool finds certified partner Kfz experts near a German postal code. It uses specific verbs ('findet', 'liefert') and resource ('Kfz-Sachverständige', 'Trefferliste'). No siblings exist, so no differentiation needed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 and when not to. It specifies the tool is for finding experts, not for filing claims or booking appointments.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!