Skip to main content
Glama

getecoback-raumklima

waeschetest_einseits_ladungswechsel_beleg

Read-only

Bei einem publizierten Trocknungsvergleich eine geänderte Ladungszusammensetzung als Beleggrenze markieren — Detect when a fabric mix changes only on one side of a drying comparison.

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": {
      "gesamt_a_g": "<gesamt_a_g>",
      "schwer_a_g": "<schwer_a_g>",
      "gesamt_b_g": "<gesamt_b_g>",
      "schwer_b_g": "<schwer_b_g>"
    },
    "name": "waeschetest_einseits_ladungswechsel_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesamt_a_gYesAusgangs-Trockenmasse der Ladung A in Gramm.
gesamt_b_gYesAusgangs-Trockenmasse der Ladung B in Gramm.
schwer_a_gYesMasse der gesondert erfassten schweren Textilgruppe in A in Gramm.
schwer_b_gYesMasse derselben Textilgruppe in B in Gramm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 detection/marking operation, but never says what a 'change only on one side' means numerically (thresholds, tolerance, which of the four masses drives the decision) or what is returned — a flag, a boolean, a boundary label. With annotations carrying safety, a 3 is appropriate.

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 German statement is front-loaded and reasonably tight, but the English second half largely restates it rather than adding information, so half the text is duplicative. Short overall, but not every clause earns 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?

All four parameters are required and fully documented, and the read-only nature is covered by annotations. However, with no output schema the definition should say what the tool produces (a boundary marker, a boolean, a textual Beleg) and how the two-sided comparison is judged; that omission leaves a real gap for a computation 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%: each of the four gram-mass parameters has a description and a 0–1,000,000 range. The description adds no meaning about how gesamt_a_g/gesamt_b_g and schwer_a_g/schwer_b_g are combined to produce the 'one-sided change' determination, so it adds nothing beyond the schema — baseline 3.

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 action and object: flagging a changed load composition (Ladungszusammensetzung) as an evidence boundary (Beleggrenze) within a published drying comparison, plus the English gloss 'detect when a fabric mix changes only on one side.' An agent can tell this is a detection/computation tool rather than a retrieval or mutation tool, though it never states the actual detection criterion or output form.

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?

Usage context is implied by 'bei einem publizierten Trocknungsvergleich' — it applies to a documented drying comparison. But there is no explicit when-to-use vs. when-not, no prerequisite (e.g. the comparison must already exist), and no routing to any of the many sibling '*_beleg' tools, so the agent must infer its place in the workflow.

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