Skip to main content
Glama

Plan buchen

plan_buchen

Bucht für eine bestehende Website einen bezahlten Plan (nur für den Inhaber des Kontos). Die Antwort enthält den Link zur Bezahlseite von Stripe mit dem Preis dieses Kontos; der Kunde öffnet ihn und bezahlt dort selbst. Nie nach Karten- oder Zahlungsdaten fragen. Welche Pläne es gibt und was sie kosten: guide mit thema «beratung». Läuft schon ein Abo, lässt sich der Plan noch nicht selbst wechseln – dann support_anfrage, wir stellen um.

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>",
      "plan": "<plan>"
    },
    "name": "plan_buchen"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYesPlan-Kennung, z. B. publish oder hosting.
websiteYesKennung oder Name der Website. Reicht der Zugang ueber mehrere Organisationen und gibt es die Kennung mehrfach, «organisation/website» schreiben.
intervallNoJährlich (Vorgabe) oder monatlich.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), it discloses what the call actually produces – a Stripe payment-page link with this account's price – and that payment happens externally, so the agent must never request card or payment data. That is exactly the kind of behavioral and safety context annotations cannot convey, and nothing contradicts the declared hints.

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?

The core action and its output are front-loaded, followed by the security warning and the escalation path, so the most decision-relevant facts come first. It is fairly dense with three distinct topics, but each sentence earns its place; only minor tightening would help.

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?

With no output schema, the description carries the burden of explaining the return value, and it does so (Stripe link plus account price). What remains thin is the plan-identification fallback and the monthly/yearly interval nuance, which the schema covers but the prose does not.

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; the description adds useful meaning on top by clarifying that website may need the «organisation/website» form (as reflected in the schema) and that this is owner-scoped. It does not discuss the intervall parameter or the plan identifier examples in prose, so it stays slightly under the schema's own richness.

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 states a specific verb and resource – booking a paid plan for an existing website – and immediately scopes it to the account owner. An agent can tell it apart from siblings like support_anfrage (used for subscription changes) and guide (used for pricing information) without opening another schema.

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 gives explicit when-to-use (booking a plan for an existing site) and when-not-to-use conditions: an already-running subscription cannot be self-switched and must go through support_anfrage, and plan/pricing questions belong to guide with thema «beratung». It also names the owner-only restriction, leaving little to inference.

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