Skip to main content
Glama

Leitfaden und Beratung

guide
Read-only

Der Leitfaden von MADLAB // Publishing, in Teilen (thema). «beratung»: was die Website HEUTE hat (Plan, Zusatzpakete, Hosting, Grenzen, Systemcheck), was wir anbieten (Pläne und Zusatzpakete mit aktuellen Preisen) und wie sich Ideen bei uns umsetzen lassen – Datenbank (SQLite), Formulare, Shop und Zahlungen, Login, Konfiguration und Schlüssel, Mehrsprachigkeit, Buchungen, Newsletter, eigene Domain – jeweils mit dem, was bei dieser Website dafür fehlt und was es kostet. ZUERST aufrufen, wenn der Kunde eine Idee hat oder fragt, ob etwas geht. «bauen»: Regeln für jede Seite (Titel, Bilder, Tempo, Auffindbarkeit, Sprachmodelle, Datenschutz). «php»: die Serverseite auf unserem Hosting – Datenbereich, config.json, SQLite, SMTP statt mail(), Uploads, Fehlersuche; vor dem ersten PHP lesen. «uebernahme»: eine bestehende Website übernehmen (ZIP oder Import) und was der Kunde vorher wissen muss. «start»: wie du das erste Gespräch führst – Schritt für Schritt, eine Frage auf einmal; aufrufen, wenn der Kunde neu ist oder noch keine Website hat. «statistik», «alles». Ohne thema: beratung und bauen.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
themaNoWelcher Teil. Ohne Angabe: beratung und bauen.
websiteNoKennung oder Name der Website. Reicht der Zugang ueber mehrere Organisationen und gibt es die Kennung mehrfach, «organisation/website» schreiben. Für die Beratung: ohne Angabe gilt die einzige Website des Kontos, bei mehreren nur der Katalog.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / thema / enum
      Previous value: -[
      -  "beratung",
      -  "bauen",
      -  "php",
      -  "uebernahme",
      -  "statistik",
      -  "alles"
      -]New value: +[
      +  "start",
      +  "beratung",
      +  "bauen",
      +  "php",
      +  "uebernahme",
      +  "statistik",
      +  "alles"
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior: the content scope of each section and the fallback rule that with multiple organizations and no `website`, counselling uses only the single account website, otherwise just the catalog. It does not describe the shape or size of the returned text, which matters for a documentation tool with no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The opening sentence is front-loaded and does orient the agent, but the body is a dense run-on with nested parentheses, guillemets and mid-sentence lists that is harder to scan than a per-section bullet structure would be. The final values 'statistik' and 'alles' are listed without any explanation, so length is not matched by even coverage.

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 two-parameter, annotation-backed, read-only documentation retrieval tool, the definition covers what it returns per section, the default selection, and the website-scoping caveat. Only the nature of the response (single long text vs. structured sections) is left unstated, a minor gap given no output schema exists.

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 100%, so the baseline would be 3, but the description earns an extra point by explaining what each enum value actually contains and why you would pick it (e.g. `php` is to be read before writing PHP, `start` for a new customer). The `organisation/website` identifier form and the counselling fallback are useful, though partly duplicated by the schema's own description.

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 states a specific resource: the MADLAB publishing guide, split into named parts via `thema`, and enumerates what each part contains (Plan/Zusatzpakete/Hosting, Bau-Regeln, PHP-Serverseite, Übernahme, Startgespräch). An agent can tell this returns reference documentation rather than performing an action. It does not explicitly contrast itself with the `hilfe` sibling, so sibling differentiation is only implicit.

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?

Usage triggers are explicit and per-section: 'ZUERST aufrufen, wenn der Kunde eine Idee hat oder fragt, ob etwas geht', 'vor dem ersten PHP lesen', 'aufrufen, wenn der Kunde neu ist oder noch keine Website hat'. The default when `thema` is omitted is also stated. What is missing is an exclusion case (when NOT to consult it, e.g. in favour of `hilfe` or `support_anfrage`).

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