Skip to main content
Glama

getecoback-raumklima

infrarot_panel_abschaltfunktion_unterlagen

Read-only

Trenne die drei dokumentierten Abschaltfunktionen eines Standpanels — Distinguish the three documented shutoff functions on a freestanding panel

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": {
      "gewuenschte_abschaltung": "<gewuenschte_abschaltung>",
      "thermostat": "<thermostat>",
      "zeitschaltung": "<zeitschaltung>",
      "kippschutz": "<kippschutz>"
    },
    "name": "infrarot_panel_abschaltfunktion_unterlagen"
  }
}

Input Schema

NameRequiredDescriptionDefault
kippschutzYesKippabhängige Abschaltung laut Hersteller
thermostatYesTemperaturabhängige Abschaltung laut Hersteller
zeitschaltungYesZeitabhängige Abschaltung laut Hersteller
gewuenschte_abschaltungYesWodurch soll das Gerät für den eigenen Ablauf abschalten?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and lookup scope are covered structurally. The description adds nothing beyond that — no indication of what the tool returns, how conflicting documentation is resolved, or what the enum outcomes mean in practice.

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?

The text is two short, front-loaded sentences with no hedging or filler. However, the second sentence is a pure English translation of the first, which duplicates content rather than adding structure or information.

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 four-required-parameter tool with no output schema, the description is minimally adequate: the schema explains the inputs, but nothing explains what the distinction produces or how a caller should act on the result. The absence of an output schema makes this a real gap rather than a minor one.

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?

With 100% schema description coverage and four fully documented enums, the schema already carries parameter meaning, so the baseline is 3. The description only loosely ties "drei dokumentierte Abschaltfunktionen" to the thermostat/Zeit/Kippschutz parameters and adds no format or interpretation detail beyond the schema.

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 concrete verb ("Trenne"/"Distinguish") and a concrete resource ("drei dokumentierten Abschaltfunktionen eines Standpanels"), so the agent knows this is a classification/distinction task on panel shutoff functions. It stops short of differentiating from siblings or stating what is produced, but the core action is identifiable.

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?

There is no statement of when to use this tool, when not to, or which alternative to pick. The only implicit cue is that the task concerns freestanding-panel shutoff functions, which an agent must infer from the name and schema rather than from the text.

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