Skip to main content
Glama

getecoback-raumklima

fachpflege_balken_mit_betriebsangebot_abgleichen

Read-only

Balkenstufe eines lesbaren P-, F- oder W-Kreises mit dem vom Reinigungsbetrieb ausdrücklich zugesagten Prozess abgleichen — Check that a quote names the same professional process and respects its mildness.

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": {
      "etikett_verfahren": "<etikett_verfahren>",
      "etikett_stufe": "<etikett_stufe>",
      "betrieb_verfahren": "<betrieb_verfahren>",
      "betrieb_stufe": "<betrieb_stufe>"
    },
    "name": "fachpflege_balken_mit_betriebsangebot_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
betrieb_stufeYesVollständig ablesbare Balkenstufe. Kein Balken = normal.
etikett_stufeYesVollständig ablesbare Balkenstufe. Kein Balken = normal.
betrieb_verfahrenYesVom Betrieb oder Etikett eindeutig benanntes professionelles Verfahren.
etikett_verfahrenYesVom Betrieb oder Etikett eindeutig benanntes professionelles Verfahren.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 safety is covered and the bar is lower. The description adds that this is a cross-check of two sources and that mildness must be "respected", but with no output schema it never says what a mismatch yields (verdict, flag, error) or how "unklar" values on either side are treated.

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 tight sentences, front-loaded with the comparison target, followed by an English restatement that meaningfully disambiguates the German phrasing rather than padding it. No wasted clauses.

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?

For a four-required-parameter read-only comparison tool with full schema coverage, what is missing is the outcome semantics: no output schema exists, so the description should have said what a passing versus failing comparison looks like. Otherwise the definition is adequate for calling the 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% and all four parameters carry enums with descriptions, so the schema does the heavy lifting and baseline 3 applies. The description adds modest framing by identifying the two comparison sides (label vs. company promise) and calling out mildness as the dimension of interest, but nothing about how etikett_* and betrieb_* are paired or what the stufe/verfahren interplay means.

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 German sentence names a specific verb ("abgleichen") and both operands: the bar level of a readable P-, F- or W-circle and the process expressly promised by the cleaning company. The English gloss ("Check that a quote names the same professional process and respects its mildness") confirms this is a comparison/consistency check rather than a reading tool, which is enough to separate it from siblings like pflegeetikett_foto_zeichenrand_und_balken or waschzeichen_grad_balken_ablesen, though those siblings are never explicitly referenced.

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?

"Check that a quote names..." implies the use case: verifying a cleaning company's offer against a care label. That is real contextual guidance but stays implicit — there is no statement of when not to use it, no mention of the reading tools that must run first to obtain the bar level, and no explicit alternatives.

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