Skip to main content
Glama

Website in Ordnung bringen

reparieren
Destructive

Behebt, was check_site im Teil SYSTEM an UNSERER Technik findet: Adresse auf die Domain des Plans ziehen, auf einen Hosting-Node ziehen, DNS-Eintrag setzen, eigene Domain neu prüfen, Eintrag im Verzeichnis auffrischen (Badge, Suchmaschinen), Zertifikat nachfragen, den veröffentlichten Stand neu übertragen. Zuerst OHNE bestaetigt aufrufen: zeigt die Schritte und ihre Folgen und ändert nichts. Das dem Kunden vorlegen und erst nach seiner Zustimmung mit bestaetigt=true ausführen. Ändert nie Dateien der Website, löscht nichts und veröffentlicht keinen Entwurf. Was so nicht behebbar ist (eine Sperre, eine vergebene Adresse, ein vom Betrieb zugemachter Weg nach draussen), sagt es mit dem Grund.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "website": "<website>"
    },
    "name": "reparieren"
  }
}

Input Schema

NameRequiredDescriptionDefault
websiteYesKennung oder Name der Website. Reicht der Zugang ueber mehrere Organisationen und gibt es die Kennung mehrfach, «organisation/website» schreiben.
bestaetigtNotrue erst, wenn der Kunde den vorgelegten Plan bestätigt hat. Ohne: nur zeigen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing a dry-run default, the list of real side effects (domain reassignment, node move, DNS, certificate request, republishing), and how unfixable cases are reported with a reason. The claim that it 'never changes website files, deletes nothing' is a refinement rather than a contradiction of destructiveHint=true, since the mutations it does perform are infrastructure-level and hard to undo.

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?

Front-loaded with purpose and the alternative-check reference, then a compact action list, then the confirmation protocol and safety limits. The action enumeration is long but each item names a distinct effect, so little is wasted; only the trailing exclusion sentence could be tightened.

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?

For a mutation tool with openWorldHint and no output schema, the description covers everything an agent needs: prerequisite, dry-run-then-confirm protocol, what changes, what is never touched, and how failures are surfaced.

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% and both parameters are already documented there, so the schema carries the baseline. The description still adds meaning by spelling out what calling without 'bestaetigt' actually produces (the step list and its consequences, with no change) and by making customer approval the condition for bestaetigt=true.

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?

Names a concrete verb (repair/fix) tied to a concrete resource and explicitly anchors the scope to what check_site reports in the SYSTEM area for 'our' technology. The enumerated repair actions (address on plan domain, hosting node, DNS entry, domain re-check, directory refresh, certificate, republish) make it unmistakable versus check_site, which only diagnoses.

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?

Gives an explicit two-phase workflow: call first without 'bestaetigt' to show the plan, present it to the customer, and only then call with bestaetigt=true. It also names the prerequisite sibling (check_site) and states which cases are out of scope (a lock, a taken address, an operationally blocked outbound path).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources