Skip to main content
Glama

Übernahme vorbereiten

import_vorbereiten
Read-only

Erster Schritt, um eine BESTEHENDE Website zu übernehmen: Gibt das Token und die zwei Wege aus, mit denen der Kunde nachweist, dass die Website ihm gehört – eine Textdatei im Webroot oder ein TXT-Eintrag im DNS. Beide Wege dem Kunden vorlegen und ihn wählen lassen; danach import_starten. Ohne diesen Nachweis beginnt kein Import. Hat der Kunde die Dateien schon, ist upload_link (ZIP) der kürzere Weg.

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>",
      "url": "<url>"
    },
    "name": "import_vorbereiten"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesStartadresse der bestehenden Website, z. B. «https://alte-seite.ch/». Gelesen werden nur ihre öffentlichen Seiten per HTTP GET, wie ein Browser sie abruft – kein API-Aufruf, keine Zugangsdaten.
websiteYesKennung oder Name der Website. Reicht der Zugang ueber mehrere Organisationen und gibt es die Kennung mehrfach, «organisation/website» schreiben.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint/openWorldHint/destructiveHint=false; the description adds real behavioral context the annotations cannot: the tool outputs a token plus two proof-of-ownership mechanisms, and the import gate is hard ('Ohne diesen Nachweis beginnt kein Import'). It does not spell out token lifetime, format, or what happens if verification is never completed, so it stops short of full disclosure.

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?

Front-loaded with the role ('Erster Schritt, um eine BESTEHENDE Website zu übernehmen'), then the outputs, then the required customer action, then the alternative. Every sentence carries information — no filler, no repetition of the title.

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?

There is no output schema, so the description compensates by naming what the tool returns (token and two verification paths) and how they are used. For a 2-parameter, fully documented, non-destructive preparation step, nothing an agent needs before calling 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 both 'url' and 'website' are already fully explained in the schema, including the HTTP-GET-only reading behavior and the 'organisation/website' disambiguation. The description itself adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource: it is the 'erster Schritt' for taking over an EXISTING website and it 'gibt das Token und die zwei Wege aus' (webroot text file or DNS TXT record). It is immediately distinguishable from import_starten and upload_link, which are named in the text.

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 sequencing and alternatives: present both verification paths to the customer and let them choose, then call import_starten; no import begins without this proof; upload_link (ZIP) is the shorter route if the customer already has the files. Both when-to-use and when-to-use-something-else are stated.

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