Skip to main content
Glama

getecoback-climate-weather

induktion_powerflex_aktivierte_rechte_zonen_beleg

Read-only

Unterscheide bei einem beobachteten PowerFlex-Vorgang zwischen einer Größenannahme, dokumentierter Zonenverbindung und unbelegter Steckbriefangabe — Confirm whether observed right-side zones were actually linked

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": {
      "modell_bestaetigt": "<modell_bestaetigt>",
      "beleg": "<beleg>",
      "angezeigte_verwendung": "<angezeigte_verwendung>",
      "gefaess_auf_beiden_rechts": "<gefaess_auf_beiden_rechts>"
    },
    "name": "induktion_powerflex_aktivierte_rechte_zonen_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
belegYesIm selben Vorgang dokumentierter Anzeigenstatus
modell_bestaetigtYesGenau Miele KM 7464 FR (11022890) und die deutsche Modellzeile in Handbuch 11 163 871 bestätigt
angezeigte_verwendungYesSelbe Zeit und rechte Seite eindeutig zugeordnet
gefaess_auf_beiden_rechtsYesEin einziges Gefäß bedeckte nach der Beobachtung beide rechten Einzelzonen

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/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 is covered. Beyond that the description adds no behavioral context: it does not say what the tool returns, how conflicting inputs are resolved, or what a 'beleg' verdict looks like.

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 clauses, front-loaded with the classification intent, with no filler. The German/English duplication is mildly redundant but does not obscure the point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and four required inputs, the description should explain what result the agent receives (a verdict, a boolean, a category). It does not, leaving the return behavior entirely unspecified for an evaluation-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% with all four parameters documented and three enums, so the schema carries the parameter meaning. The description adds no additional semantics for the individual fields, which is the expected baseline here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a classification task (distinguishing a size assumption, a documented zone link, and an unsupported spec-sheet claim) and a confirmation goal for observed right-side zones. However, it never states what the tool actually produces or how the four inputs combine into a verdict, so the operation stays abstract.

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 guidance on when to use this tool versus the many sibling evidence/zone tools, and no prerequisites or exclusions are given. The agent must infer the triggering situation entirely from the name and description.

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