Skip to main content
Glama

getecoback-raumklima

dunstabzug_metall_kohle_pflegeauftrag_abgrenzen

Read-only

Ordne einen belegten Geschirrspülerhinweis nur dem tatsächlich benannten Metallfettfilter zu — Keep grease-filter dishwasher evidence separate from carbon-filter care

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": {
      "de_modell_dwb66bc50": "<de_modell_dwb66bc50>",
      "beobachtetes_teil": "<beobachtetes_teil>",
      "teil_material_belegt": "<teil_material_belegt>"
    },
    "name": "dunstabzug_metall_kohle_pflegeauftrag_abgrenzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
beobachtetes_teilYesWelches Teil soll im Pflegeplan erscheinen?
de_modell_dwb66bc50YesDeutsches Bosch-Datenblatt DWB66BC50 gehört zur Haube
teil_material_belegtYesGenaue Baugruppe und Filterart lassen sich vor Ort eindeutig unterscheiden

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 declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the meaningful behavioral rule that grease-filter dishwasher evidence must not bleed into carbon-filter care, but it says nothing about the result of the assignment (what is returned, whether 'offen'/'beide' paths yield a refusal or a partial mapping). No outright contradiction with the read-only annotation, since 'zuordnen' here reads as classification rather than a write.

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 operative constraint is front-loaded, but the description gives the same content twice in German and English, which adds length without adding information. The dash structure reads like a gloss rather than a purposeful split.

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 no output schema, the definition is minimally sufficient to select the tool. What is missing is the outcome contract: with the enum including 'beide' and 'offen', the agent has no idea how those cases are handled or what the tool returns for them.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description genuinely adds to parameter meaning: "nur dem tatsächlich benannten" tells the agent that beobachtetes_teil should be set to the explicitly named part rather than defaulting to 'beide', and "belegt" signals that teil_material_belegt must be a substantiated finding. It still does not explain how the two boolean preconditions gate the outcome.

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 action ("Ordne ... zu") and a specific resource (a documented dishwasher note / grease-filter evidence bound to the metal grease filter), and it states the separation goal against carbon-filter care. However, the phrasing "Geschirrspülerhinweis" is opaque in a range-hood context and it never says concretely what gets produced — a classification decision, a care-plan entry, or a validation verdict. An agent can guess the domain but not the precise operation.

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 constraint "nur dem tatsächlich benannten Metallfettfilter" implies the use case: evidence should be attributed only when the part is explicitly named. There is no explicit when-to-use vs when-not framing and no sibling is named, so the agent must infer which of the many dunstabzug_* delineation tools this replaces.

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