Skip to main content
Glama

getecoback-raumklima

spuelinformationsmenue_auslesefelder_geraetevermerk

Read-only

Bei einer Geräteübergabe Zählerfelder, Modellbezug und Softwarevermerk getrennt dokumentieren — Select the proper information field for the intended reference.

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": {
      "genaues_miele_handbuch": "<genaues_miele_handbuch>",
      "zweck": "<zweck>",
      "aufgezeichnetes_feld": "<aufgezeichnetes_feld>"
    },
    "name": "spuelinformationsmenue_auslesefelder_geraetevermerk"
  }
}

Input Schema

NameRequiredDescriptionDefault
zweckYesWelche Belegart wird für die Übergabenotiz gesucht?
aufgezeichnetes_feldYesTatsächlich abgelesenes Feld.
genaues_miele_handbuchYesDas bezeichnete Informationsmenü ist in der Anleitung des Geräts belegt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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. The description adds almost nothing beyond that: it does not say whether the boolean 'belegt im Handbuch' gates the result, what happens with 'unklar', or what is returned. 'Dokumentieren' also mildly implies recording/writing, which sits in tension with readOnlyHint, though not clearly enough to call a contradiction.

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 compact clauses with no filler, and the documentary scenario is front-loaded. The mixed German/English phrasing and the unexplained term 'intended reference' cost a little precision rather than length.

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?

A three-parameter, all-required tool with no output schema should say more: what the call returns (a resolved field? a classified record type?), how 'unklar' and the manual-evidence boolean affect the outcome, and when to prefer a sibling. The description leaves the core output behavior entirely unspecified.

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 two of three parameters have documented enums, so the schema carries the semantics. The description contributes no additional meaning about 'zweck', 'aufgezeichnetes_feld', or the 'genaues_miele_handbuch' flag — notably it never clarifies how the manual-evidence boolean interacts with the selection. Baseline 3 is appropriate.

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 specific context (device handover) and a resource set (counter fields, model reference, software note) and says to 'dokumentieren' them separately. However, the second sentence — 'Select the proper information field for the intended reference' — is vague (what is an 'intended reference'?) and never states whether the tool reads the fields, classifies them, or resolves which one applies. An agent cannot confidently distinguish this from siblings like spuelbeleg_umzug_geraetevermerk_von_raumlabel_trennen.

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

Usage Guidelines3/5

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

The opening clause implies the usage situation (during a device handover, to document fields separately), which is a usable context cue. There is no explicit when-to-use, no when-not-to-use, and no named alternative among the many similarly-named sibling tools, so selection still relies on inference from the period-example sentence.

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