Skip to main content
Glama

Name, Beschreibung und Adresse

website_einstellungen
Destructive

Zeigt oder ändert Name, Beschreibung und Adresse (Kennung vor .freesite.space bzw. .madsite.ch) einer Website. Ohne name, beschreibung und kennung: nur anzeigen. Vor der ersten Veröffentlichung ist die Adresse frei änderbar. Danach zieht sie um – die alte leitet ein Jahr lang weiter, und das geht nur begrenzt oft: zuerst OHNE «bestaetigt» aufrufen, die Vorlage dem Kunden zeigen und erst nach seinem Ja mit bestaetigt: true. Die Beschreibung (wovon die Website handelt, in seinen Worten) hilft jedem späteren Gespräch.

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": "website_einstellungen"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNeuer Name, wie ihn der Kunde nennt (2–120 Zeichen).
kennungNoNeue Adresse, nur der Teil vor der Domain: Kleinbuchstaben, Ziffern, einzelne Bindestriche, 3–40 Zeichen.
websiteYesKennung oder Name der Website. Reicht der Zugang ueber mehrere Organisationen und gibt es die Kennung mehrfach, «organisation/website» schreiben.
bestaetigtNoNur für den Umzug einer VERÖFFENTLICHTEN Adresse, und erst nachdem der Kunde zugestimmt hat.
beschreibungNoWovon die Website handelt, ein, zwei Sätze (höchstens 300 Zeichen). Leer = keine.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare destructiveHint=true, and the description justifies it with real consequences: after publication the old address redirects for one year and can only be moved a limited number of times. It additionally discloses a mandatory customer-consent workflow that the annotations cannot express.

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?

The display-or-modify rule comes first, followed by the address-change procedure and the rationale for the description field. Every sentence carries operational information; nothing is redundant.

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?

For a destructive mutation tool with no output schema, it covers consequences, consent requirements, and the limited-move constraint well. It is slightly incomplete on failure modes, e.g. what happens once the move limit is exhausted or whether the old address reverts.

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 the baseline is 3; the description still adds value by linking 'kennung' to the address prefix and to the one-year redirect behavior, and by tying 'bestaetigt' to the consent step. It does not add format details beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb pair and resource: 'Zeigt oder ändert Name, Beschreibung und Adresse ... einer Website', and clarifies that the address is only the part before the domain suffix. It does not explicitly contrast itself with siblings such as website_anlegen, so it stops short of full sibling differentiation.

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?

It states the read-only trigger explicitly ('Ohne name, beschreibung und kennung: nur anzeigen') and gives a concrete two-step procedure for address changes: call first without 'bestaetigt', show the draft to the customer, then call again with 'bestaetigt: true' after consent. It also warns that moves are only possible a limited number of times after publication.

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