Skip to main content
Glama

hvac-btu-heat-klimaanlage

ratgeber_lesen

Liest die redaktionelle Textansicht eines veröffentlichten Ratgebers. — Reads the cleaned Markdown of a published guide, with reviewed source links, assumptions and limits. Long excerpts are explicitly marked and link the full text. Pass an exact canonical path or URL from ratgeber_suche, without query or fragment.

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": {
      "pfad": "<pfad>"
    },
    "name": "ratgeber_lesen"
  }
}

Input Schema

NameRequiredDescriptionDefault
pfadYesPfad oder vollständige URL, z. B. /guide/klimaanlage-kippfenster.html

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the return shape (reviewed source links, assumptions, limits, long excerpts marked with links to the full text) and that only published guides are served, but it says nothing about failure behavior, whether access is unrestricted, or caching/freshness. Adequate but with clear gaps for an un-annotated tool.

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?

Purpose is front-loaded and every clause carries information (provenance, format constraints, return characteristics). The German/English duplication roughly doubles the length, which is understandable for a bilingual tool but is still redundancy an agent must parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no output schema this is close to sufficient: it describes what comes back and where the input must come from. Missing error/edge-case behavior and any note that the operation is a pure read keep it from being complete.

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 is 3, but the description adds real constraints the schema does not: the path must be exact/canonical, must originate from ratgeber_suche, and must exclude query strings and fragments. That is meaningful semantics beyond the schema's bare example.

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 gives a specific verb and resource ('Liest die redaktionelle Textansicht eines veröffentlichten Ratgebers' / 'Reads the cleaned Markdown of a published guide'), which is far more concrete than the bare name ratgeber_lesen. It implicitly distinguishes the tool from the sibling ratgeber_suche by requiring input that search produces, though it never explicitly states the contrast. Good, but not fully differentiated in so many words.

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 tells the agent where the argument comes from ('Pass an exact canonical path or URL from ratgeber_suche') and what form it must take (no query or fragment), which routes the agent to the search sibling first. It stops short of stating when-not to use this tool or what happens with a stale/invalid path.

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.