Skip to main content
Glama

getecoback-climate-weather

dunstabzug_dkf16p_zweierpack_einsatznachweis

Read-only

Trenne eine dokumentierte Packung für die DA 7006 D von einem einzeln aufgefundenen DKF 12-P — Verify the documented two-piece DKF 16-P pack before counting a complete replacement

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": {
      "da7006_d_belegt": "<da7006_d_belegt>",
      "beleg_material_11762660": "<beleg_material_11762660>",
      "dkf12p_eindeutig_gefunden": "<dkf12p_eindeutig_gefunden>",
      "ungepruefte_teile": "<ungepruefte_teile>"
    },
    "name": "dunstabzug_dkf16p_zweierpack_einsatznachweis"
  }
}

Input Schema

NameRequiredDescriptionDefault
da7006_d_belegtYesHaube ist als Miele DA 7006 D bestätigt
ungepruefte_teileYesWeitere Filter in derselben Packung, deren genaue Kennung noch offen ist
beleg_material_11762660YesPaket zeigt DKF 16-P / Materialnummer 11762660
dkf12p_eindeutig_gefundenYesTatsächlich als DKF 12-P identifizierte Filter aus dieser Packung

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that this is a gating verification step before a replacement is counted, but it never states what the tool returns (a verdict? a count?) or what happens when the pack is not documented.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and the constraint is front-loaded, but the German and English clauses restate the same idea rather than adding information, so half the text is redundant rather than earning its place.

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?

Four required parameters, no output schema, and read-only annotations mean the description should explain the decision it produces. It explains the intent but not the outcome, leaving the agent unsure what a successful call actually establishes.

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, so the schema carries parameter meaning. The description only alludes to two of them (documented pack, single DKF 12-P find) and adds no interpretation of 'ungepruefte_teile' or how the booleans combine into a decision.

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 gives a verb ('Trenne'/'Verify') and the objects being separated — a documented two-piece DKF 16-P pack versus a single DKF 12-P find — but the mixed German/English wording and the DKF 12-P/DKF 16-P overlap make the exact scope of the check hard to pin down. It does not name or contrast any sibling tool, so an agent cannot route on the description alone.

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?

'before counting a complete replacement' implies the moment of use (a counting/verification gate), which is real but implicit guidance. There is no statement of when NOT to use it, no prerequisites, and no named alternative among the many dunstabzug_* siblings.

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