Skip to main content
Glama

getecoback-climate-weather

comfoair_q_handbuch_nutzerpflege_oder_fachservice

Read-only

Ordnet eine konkrete Anfrage zur Bedienerpflege oder zum Fachservice der passenden Handbuchstelle zu — Route a recorded care request to the user manual or professional service.

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": {
      "aufgabe": "<aufgabe>",
      "ausgabe_passt": "<ausgabe_passt>"
    },
    "name": "comfoair_q_handbuch_nutzerpflege_oder_fachservice"
  }
}

Input Schema

NameRequiredDescriptionDefault
aufgabeYesGewünschte Tätigkeit.
ausgabe_passtYesExterne Gerätekennzeichnung und diese Ausgabe der deutschen Q-Benutzeranleitung passen zusammen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds no behavioral detail about the outcome — notably what the tool does when 'ausgabe_passt' is false (refuse, escalate, or route to Fachservice) and what form the 'Handbuchstelle' answer takes.

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?

A single front-loaded sentence with the action stated first and the resource second; no filler. The German/English duplication is mildly redundant but standard for bilingual catalogs.

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?

Two required parameters with full schema coverage make this simple, but with no output schema the description should indicate what a routing result looks like (manual section identifier vs. service referral). That return-side gap leaves it only adequate.

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 both parameters and the enum are fully documented structurally; baseline is 3. The description adds no extra meaning about the taxonomy of tasks or the role of the 'ausgabe_passt' compatibility gate.

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+object: it assigns ("Ordnet ... zu") a concrete care request to the matching manual section or professional service. The routing action is distinct from every sibling, which deal with unrelated measurement/record tasks, so an agent can identify the tool without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not guidance beyond the implied "a concrete request exists." Nothing says what happens with the 'offen' enum value or how this differs from handling the care task directly, leaving selection to inference.

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