Skip to main content
Glama

Neue Website anlegen

website_anlegen

Legt eine neue Website an: Name, kurze Beschreibung, Adresse (Kennung vor .freesite.space) und Plan – dieselben Felder wie im Portal. Ohne Kennung wird eine aus dem Namen vorgeschlagen. Die Adresse ist danach reserviert, und veröffentlicht wird zuerst kostenlos auf freesite.space. Name, Beschreibung und Adresse VORHER mit dem Kunden klären (Vorschläge machen). Ein bezahlter Plan (nur für den Inhaber des Kontos): die Antwort enthält einen Link zur Bezahlseite von Stripe, den der Kunde selbst öffnet – nie nach Karten- oder Zahlungsdaten fragen. Bei mehreren Konten «konto» angeben.

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": {
      "name": "<name>"
    },
    "name": "website_anlegen"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName der Website, wie ihn der Kunde nennt (2–120 Zeichen).
planNoPlan-Kennung (z. B. free, publish, hosting). Vorgabe: free. Welche es gibt und was sie kosten: guide mit thema «beratung».
kontoNoKennung oder Name des Kontos. Nur nötig, wenn der Zugang auf mehrere reicht.
kennungNoAdresse vor .freesite.space: Kleinbuchstaben, Ziffern, einzelne Bindestriche, 3–40 Zeichen. Leer = Vorschlag aus dem Namen.
intervallNoFür einen bezahlten Plan: jährlich (Vorgabe) oder monatlich.
beschreibungNoWovon die Website handelt, ein, zwei Sätze (höchstens 300 Zeichen).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds substantial behavior beyond that: the address is reserved after creation, publishing is initially free on freesite.space, and a paid plan returns a Stripe payment-page link the customer opens themselves. It also draws an explicit safety boundary – never ask for card or payment data – which is exactly the kind of constraint 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.

Conciseness4/5

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

Front-loaded with the purpose, then the field list, then behavior and safety constraints. Dense and mostly earning its space, though 'dieselben Felder wie im Portal' is filler and the customer-clarification and account-handling sentences 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 6-parameter mutation tool with no output schema, the definition covers the ambiguous parts an agent would otherwise guess at: slug suggestion, address reservation, free-first publishing, the Stripe redirect flow, and the multi-account case. Nothing needed to invoke it correctly is missing.

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 every parameter is already documented, including the kennung fallback and the intervall enum. The description mostly restates the field set ('dieselben Felder wie im Portal') and repeats the slug-from-name suggestion already in the schema, adding only the paid-plan/Stripe context. 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?

Names a specific verb and resource ('Legt eine neue Website an') and enumerates the fields it sets: Name, Beschreibung, Adresse (Kennung vor .freesite.space), Plan. This is distinguishable from website_einstellungen (later edits) or plan_buchen without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete preconditions and workflow: clarify name, description and address with the customer beforehand, propose suggestions, and pass «konto» only when the access spans multiple accounts. It stops short of explicitly routing to alternatives (e.g. plan booking or later settings changes), so it is clear context without full when-not guidance.

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