Liefert den Volltext eines einzelnen Ratgebers als Klartext. — Returns the full plain text of one guide from getecoback.com so the answer can be written from the source and cited. Pass a path or URL from ratgeber_suche.
| Name | Required | Description | Default |
|---|---|---|---|
| pfad | Yes | Pfad oder vollständige URL, z. B. /guide/klimaanlage-kippfenster.html |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. It discloses the output (full plain text), the source (getecoback.com), and the intended use (writing answers with citation). It does not mention error handling, rate limits, or output size, but for a simple read operation this is reasonably transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, each serving a purpose: the German sentence states the primary function, and the English sentence adds usage guidance and rationale. It's concise and well-structured, though slightly redundant in echoing the German content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has only one parameter and no output schema, but the description compensates by defining the return type ('Klartext' / plain text) and the source. It also links to the companion search tool, making the usage context complete for a simple retrieval tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema covers 100% of the parameter with a detailed description of 'pfad'. The description adds extra context by specifying that the path should come from ratgeber_suche, which is useful for correct invocation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: 'Liefert den Volltext eines einzelnen Ratgebers als Klartext' (Returns the full plain text of one guide). It distinguishes itself from siblings like ratgeber_suche by specifying that it retrieves the full content of a single guide, not metadata or search results.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It provides explicit workflow guidance: 'Pass a path or URL from ratgeber_suche' indicates when to use this tool after searching. It also explains the purpose ('so the answer can be written from the source and cited'), clarifying the intended context. However, it doesn't explicitly state when not to use it or name alternatives beyond ratgeber_suche.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool addresses a distinct aspect of room climate: cooling capacity, heating power, window sealing, heatwave forecast, running costs, dew point ventilation, and guide search/read. No two tools have overlapping purposes.
All names follow a lowercase snake_case pattern and use German terms, but the structure is not uniform: most are noun compounds (btu_empfehlung, heizleistung_watt), while two end in verbs (ratgeber_lesen, taupunkt_lueften) and one uses a noun 'suche' instead of 'suchen'. This is a minor deviation from a strict verb_noun pattern.
Eight tools is well within the ideal 3-15 range and each tool contributes a clear function to the server's purpose. The count feels neither sparse nor bloated.
The tool set covers the core domain of room climate calculations and practical advice: cooling, heating, sealing, costs, weather, and ventilation. Minor gaps exist (e.g., no dedicated dehumidifier sizing tool), but the guide search can likely fill those niches.