Skip to main content
Glama

getecoback-raumklima

induktion_erkennung_wechselseitige_probe_zuordnung

Read-only

Lies zwei bereits beobachtete Gefäße in zwei Einzelzonen als Wechselprobe, um einen gefäß- oder zonengebundenen Hinweis zu unterscheiden — Interpret a paired cookware–zone recognition swap

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": {
      "gefaess_a_zone_1": "<gefaess_a_zone_1>",
      "gefaess_a_zone_2": "<gefaess_a_zone_2>",
      "gefaess_b_zone_1": "<gefaess_b_zone_1>",
      "gefaess_b_zone_2": "<gefaess_b_zone_2>",
      "erkennungsbedingungen_gleich": "<erkennungsbedingungen_gleich>"
    },
    "name": "induktion_erkennung_wechselseitige_probe_zuordnung"
  }
}

Input Schema

NameRequiredDescriptionDefault
gefaess_a_zone_1YesBeobachtung für A auf Zone 1
gefaess_a_zone_2YesBeobachtung für A auf Zone 2
gefaess_b_zone_1YesBeobachtung für B auf Zone 1
gefaess_b_zone_2YesBeobachtung für B auf Zone 2
erkennungsbedingungen_gleichYesZwei verschiedene Einzelzonen und zwei Gefäße, jeweils gleicher Erkennungsmodus, mittige Platzierung und dokumentierte Bodenbereiche

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint=true and openWorldHint=false annotations match the description's framing as a pure interpretation of recorded observations, so no contradiction exists. The description usefully adds that the tool reasons over pre-existing data under equal detection conditions, but it never says what the interpretation produces (a vessel-bound, zone-bound, or indeterminate verdict), which matters because there is no output schema.

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 diagnostic purpose and the precondition are front-loaded in a single German sentence, with the English gloss appended. The English clause largely duplicates the German rather than adding information, which is minor waste but not damaging.

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?

All five required parameters are fully described in the schema, so an agent can construct a valid call. However, for an analytic tool with no output schema, the description should indicate what conclusions come back and how ties or 'unbeobachtet' cases are resolved; that is the one real gap.

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% and the four enum parameters are fully self-documenting, so the schema carries the parameter burden. The description only restates the two-vessels-by-two-zones structure already encoded in the field names and adds no syntax or interpretation hints beyond that, making the baseline 3 appropriate.

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 — reading two already-observed vessels in two individual zones as a swap test — and names the diagnostic goal (distinguishing a vessel-bound from a zone-bound indication). That is far more specific than the tool name alone. It stops short of naming which sibling to use instead (e.g. the two-vessel exclusive-zone or heat-profile tools), so it is clear but not sibling-differentiating.

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?

The phrase 'bereits beobachtete' establishes a clear precondition: this tool interprets existing observations rather than running a live test, and the stated goal (vessel- vs zone-bound) implies when the swap design is the right one. There is no explicit when-not guidance and no alternative tool is named, which keeps it below a 5.

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