turbopress

Website diagnostizieren

diagnose_website

Read-only

Aggregiert alle relevanten Signale einer Domain (live: HTTP-Erreichbarkeit, SSL, Speicherplatz, Datenbanken, fatale PHP-Fehler aus dem Fehlerprotokoll; aus dem letzten Report: Security, DNS, CloudLinux, WordPress) zu EINER priorisierten Hauptdiagnose statt vieler Einzelantworten. Ideal für "meine Seite ist kaputt/langsam, was ist los?" statt mehrere Tools einzeln aufzurufen. Das Protokoll wird im Moment der Abfrage gelesen und nach "PHP Fatal error" und "PHP Parse error" durchsucht, gemeldet werden nur Treffer aus den letzten 48 Stunden — eine Protokolldatei umspannt Monate, ältere Zeilen sind kein aktuelles Problem. Kein Treffer heißt also "nichts in diesem Zeitraum", nicht "nie ein Fehler"; ältere nennt die Antwort im Fußtext. War das Protokoll nicht lesbar, sagt die Antwort das ausdrücklich — dann ist ein PHP-Fehler offen, nicht ausgeschlossen. Andere Meldungen (Warnungen, Hinweise) oder ein eigenes Suchmuster: search_domain_error_log.

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": {
      "domain": "<domain>"
    },
    "name": "diagnose_website"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Die Domain, z. B. example.com

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 13, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedOct 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare readOnly/openWorld/non-destructive; the description adds substantial behavior beyond them: the log is read at query time, only the last 48 hours are reported, a no-hit result means 'nothing in this window' rather than 'never an error', and an unreadable log is explicitly reported as an open (not excluded) PHP error. This is exactly the interpretive context an agent needs.

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?

Front-loaded with purpose and usage scenario, then dense edge-case semantics. It is long (multiple sentences) but nearly every sentence earns its place by clarifying result interpretation; a slightly tighter phrasing of the log-window caveats could still trim length.

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 diagnostic aggregator with no output schema, the description covers what is aggregated, the live vs. report sources, and the crucial interpretation caveats (48h window, unreadable log, footer note about older errors). Nothing an agent needs to call and interpret it correctly 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% and there is a single 'domain' parameter, so the schema already carries the semantics. The description adds no format/syntax detail for the parameter beyond what the schema provides, so the baseline 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?

The description states a specific verb+resource ('aggregiert alle relevanten Signale einer Domain ... zu EINER priorisierten Hauptdiagnose') and immediately delimits itself from the many single-signal siblings by naming search_domain_error_log as the tool for other log queries. An agent can tell what this tool is and what it is not without opening any 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 an explicit trigger scenario ('meine Seite ist kaputt/langsam, was ist los?') and explicitly contrasts the approach with calling several individual tools. It also routes a specific alternative case (warnings/notices or custom patterns) to search_domain_error_log.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All turbopress tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?