Skip to main content
Glama

Vorschau-Adresse

preview
Destructive

Gibt eine Adresse, unter der sich der aktuelle Stand ansehen lässt, ohne ihn zu veröffentlichen. Wie lange sie gilt, steht in der Antwort – in den meisten Plänen kurz, also zum Anschauen und nicht zum Verschicken.

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

Input Schema

NameRequiredDescriptionDefault
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.0
Behavior4/5

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

The annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=true, so the safety profile is partly covered; the description's real added value is that the response carries the validity period, which is typically short depending on the plan — important since no output schema exists. It does not explain why the operation is flagged destructive (e.g. whether a new preview invalidates an older link) or how publicly reachable the address is, despite openWorldHint=true.

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?

Two sentences, zero waste: the core promise comes first and the expiry caveat follows as a practical constraint. Nothing needs to be re-read or inferred from length.

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 one-parameter tool with no output schema and rich annotations, the description covers what the result is and how long it lasts, which is the main thing an agent needs. The remaining gap is behavioral: no mention of what the destructive flag implies or whether repeated calls replace earlier preview links.

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?

The single parameter has 100% schema description coverage, including the «organisation/website» disambiguation for multi-org access, so the schema does the heavy lifting. The description adds no extra meaning about the website identifier, so the high-coverage baseline of 3 applies.

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 names a concrete outcome — an address under which the current state can be viewed without publishing it — which is more specific than the title 'Vorschau-Adresse' alone. It implicitly separates itself from the publishing siblings ('ohne ihn zu veröffentlichen') but never names a sibling such as publish or publish_status explicitly.

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?

It gives a clear usage context (inspect the current state without going live) and even a when-not-to-use signal: the short validity means the link is for viewing, 'nicht zum Verschicken'. It stops short of naming an alternative tool for cases where a durable or public link is actually wanted.

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