Skip to main content
Glama

getecoback-climate-weather

thermostat_adapter_pruefbeleg_zuordnen

Read-only

Eine dokumentierte Thermostat-Passprobe mit oder ohne Adapter getrennt ausweisen — Separate observed fit with an adapter from direct-fit evidence.

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": {
      "ventil_und_kopf_exakt": "<ventil_und_kopf_exakt>",
      "testaufbau": "<testaufbau>",
      "adapter_exakt": "<adapter_exakt>"
    },
    "name": "thermostat_adapter_pruefbeleg_zuordnen"
  }
}

Input Schema

NameRequiredDescriptionDefault
testaufbauYesBei der dokumentierten Passprobe verwendet.
adapter_exaktYesBei Adapterbetrieb genaue Adapterbezeichnung erfasst?
ventil_und_kopf_exaktYesVentil, Kopf und Generation im Protokoll identifiziert?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is known. The description adds the domain behavior of separating adapter-based from direct-fit evidence, but it does not explain how the inputs lead to classification or what is reported.

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 description is a single front-loaded sentence with a useful English translation. The bilingual repetition is slightly redundant, but the wording is otherwise compact and free of padding.

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?

With three fully documented required parameters and read-only annotations, the definition covers the inputs adequately. However, there is no output schema and the description does not explain what is returned or how the separation is represented, leaving a meaningful gap for a classification-style tool.

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 the schema already documents all three parameters, including the enum values and boolean fields. The description does not add syntax, format, or interaction semantics beyond what the schema provides.

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 states a specific operation: separating observed thermostat fit evidence with an adapter from direct-fit evidence. It is clear enough to distinguish the tool's purpose, though it does not name or differentiate any sibling tools.

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 explicit guidance on when to use this tool versus alternatives, nor any when-not conditions. The domain context implies it is used when documenting thermostat fit tests, but the description leaves the agent to infer this.

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