Skip to main content
Glama

getecoback-raumklima

dampfreiniger_sc2_maximaldruck_dauermessung

Read-only

Unterscheide beim SC 2 EasyFix maximalen Dampfdruck und den belegten Druck bei einer Arbeitsstufe — Separate maximum steam pressure from a documented SC 2 operating measurement

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": {
      "artikel_15126000": "<artikel_15126000>",
      "leistungsangabe": "<leistungsangabe>",
      "angabe_bar": "<angabe_bar>",
      "gleiche_stufe_und_protokoll": "<gleiche_stufe_und_protokoll>"
    },
    "name": "dampfreiniger_sc2_maximaldruck_dauermessung"
  }
}

Input Schema

NameRequiredDescriptionDefault
angabe_barYesGefundener Druckwert in bar
leistungsangabeYesArt der vorliegenden Druckangabe
artikel_15126000YesSC 2 EasyFix mit Händlerreferenz 1.512-600.0 eindeutig identifiziert
gleiche_stufe_und_protokollYesMessstelle, Stufe und beobachtete Dauer des Arbeitsvorgangs sind belegt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 known without the description. The description contributes the domain framing of what is being separated, which is the tool's actual behaviour, but it says nothing about what happens when gleiche_stufe_und_protokoll is false or how a mismatch between the claimed and documented reading is handled.

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?

The front-loaded German sentence carries the meaning efficiently, but the English sentence is a near-verbatim translation of the same content rather than new information. The duplication inflates length without adding signal, leaving the description partially wasteful.

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?

There is no output schema, so the description carries the burden of explaining what the call yields, and it does not: an agent cannot tell whether it receives a boolean, a classification label, or a corrected bar value. For a four-required-parameter judging tool this leaves a real gap in interpreting the result.

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%, so all four parameters, including the leistungsangabe enum with its maximalwert/messwert_arbeitsstufe/offen values, are already fully documented in the schema. The description's max-versus-operating-stage framing mirrors that enum without adding format, boundary, or dependency detail beyond it, making the baseline 3 correct.

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 names a specific operation on a specific device (SC 2 EasyFix) and states the conceptual distinction it draws: maximum steam pressure versus a documented pressure at an operating stage. It is far more specific than the bare tool name, though it never states the concrete outcome (a label, a validation verdict, a corrected figure), so the agent knows the topic but not the product.

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 when-to-use or when-not-to-use guidance and no reference to any alternative tool. The only routing cue is implicit in the German verb 'Unterscheide', which hints this is a classification step, but nothing tells the agent under which conditions to call it rather than another dampfreiniger sibling.

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