Skip to main content
Glama

hvac-btu-heat-klimaanlage

ratgeber_suche

Durchsucht veröffentlichte Ratgeber mit lesbarer Textansicht. — Searches published guides with a readable Markdown mirror, returning title, canonical URL and task-specific summary. Every result can be passed to ratgeber_lesen.

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": {
      "frage": "<frage>"
    },
    "name": "ratgeber_suche"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoAnzahl Treffer (1–10, Default: 5)
frageYesSuchbegriff oder Frage — search term or question, German or English, e.g. 'Klimaanlage Kippfenster abdichten' or 'portable ac tilt window'
spracheNoNur deutsche oder nur englische Seiten (Default: beide)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / frage / description
      Previous value: -"Suchbegriff oder Frage, z. B. 'Klimaanlage Kippfenster abdichten' oder 'portable ac tilt window'"New value: +"Suchbegriff oder Frage — search term or question, German or English, e.g. 'Klimaanlage Kippfenster abdichten' or 'portable ac tilt window'"
  2. Added

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does disclose the return shape and that only guides with a readable Markdown mirror are indexed, but it says nothing about result ordering/relevance ranking, empty-result behavior, or the fact that this is a read-only, non-mutating lookup.

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?

Two short sentences, front-loaded with what the tool does and followed by the downstream workflow hint. The only waste is the German/English duplication of the same content, which serves a bilingual audience but halves the density.

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 3-parameter read-only search tool with fully described schema and no output schema, the description covers purpose, indexed corpus, return fields, and the follow-up tool. Only ranking/empty-result behavior is left unstated, a minor gap at this complexity level.

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%, so all three parameters (frage, max, sprache) are already documented in the schema. The description adds no extra meaning about matching semantics (is it keyword, full-text, or semantic search?) or how the default result count interacts with usage, 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?

States a specific verb and resource ('Durchsucht veröffentlichte Ratgeber' / 'Searches published guides') plus a scope constraint (only guides with a readable Markdown mirror), and names the exact return fields (title, canonical URL, summary). It also distinguishes itself from the sibling ratgeber_lesen by positioning itself as the entry step whose results feed that tool.

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?

'Every result can be passed to ratgeber_lesen' defines a clear two-step workflow and gives the agent an actionable next move after calling this tool. It does not, however, state when-not to use it or contrast it with the calculator-style siblings (btu_empfehlung, geraet_wahl), leaving that inference to the agent.

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.