Skip to main content
Glama

Wohin veröffentlicht wird

veroeffentlichungsziel

Zeigt oder wählt, wohin eine Website veröffentlicht wird. aktion «zeigen» (Vorgabe): unser Hosting (Adresse) oder ein eigener Server (FTP/SFTP) samt Stand der letzten Prüfung, und was der Plan erlaubt. «madlab»: auf unser Hosting wechseln – kommt die Website von einem eigenen Server, zuerst OHNE bestaetigt aufrufen, dem Kunden vorlegen, dann mit bestaetigt=true. «eigenes»: sagt, wo der Kunde seinen eigenen Server im Portal einträgt – die Zugangsdaten (Host, Benutzer, Passwort) NIE im Chat erfragen oder entgegennehmen. «pruefen»: testet die Verbindung zum eingetragenen eigenen Server.

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

Input Schema

NameRequiredDescriptionDefault
aktionNoWas tun. Vorgabe: zeigen.
websiteYesKennung oder Name der Website. Reicht der Zugang ueber mehrere Organisationen und gibt es die Kennung mehrfach, «organisation/website» schreiben.
bestaetigtNoNur für «madlab» von einem eigenen Server weg, nach dem Ja des Kunden.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The annotations declare this is not read-only, and the description adds important behavioral context: the «madlab» switch may require a dry run without bestaetigt followed by a confirmed call after customer approval. It also discloses that plan limits affect the result, that credentials must not be handled in chat, and that «pruefen» performs a live connection test.

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 description is front-loaded with the core purpose and then organizes details by action label. Every sentence contributes operational or safety-relevant information, with no filler.

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 three-parameter configuration tool with no output schema, the description covers the decision workflow, safety constraints, plan restrictions, and connection testing. An agent has enough information to choose the right action and invoke it correctly.

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 already 100%, so the baseline is 3, but the description adds real meaning by explaining what each enum value of aktion does. It also clarifies that bestaetigt is only for the «madlab» switch away from a customer-owned server and only after customer approval.

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?

The description gives a specific resource and clearly scopes the tool to publication target configuration rather than publishing itself. It enumerates all four modes, so an agent can distinguish showing, switching to provider hosting, configuring a customer server, and testing a connection.

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?

Each action has explicit guidance: «zeigen» for status, «madlab» for switching to provider hosting with a two-step confirmation flow, «eigenes» for where the customer enters server details, and «pruefen» for connection testing. It also gives a hard rule never to request or accept credentials in chat.

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