Skip to main content
Glama

getecoback-climate-weather

heizwaesche_untersuchte_flaechenproben_minimum

Read-only

Zeitgleich geprüfte Teile und ungeprüfte Positionen nach Ständerzone trennen — Check whether observed zone coverage is sufficient for a load-wide conclusion.

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": {
      "teile_lueckenlos_zugeordnet": "<teile_lueckenlos_zugeordnet>",
      "oben_gesamt": "<oben_gesamt>",
      "oben_bestaetigt": "<oben_bestaetigt>",
      "unten_gesamt": "<unten_gesamt>",
      "unten_bestaetigt": "<unten_bestaetigt>"
    },
    "name": "heizwaesche_untersuchte_flaechenproben_minimum"
  }
}

Input Schema

NameRequiredDescriptionDefault
oben_gesamtYesStücke in der oberen betrachteten Lage.
unten_gesamtYesStücke in der unteren betrachteten Lage.
oben_bestaetigtYesDavon wirklich und sicher am Ziel bestätigte Stücke.
unten_bestaetigtYesDavon wirklich und sicher am Ziel bestätigte Stücke.
teile_lueckenlos_zugeordnetYesSind alle vorhandenen Positionen und untersuchten Stücke eindeutig zugeordnet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/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. Beyond that, the description only hints at a decision ('sufficient') without stating what the tool returns, how the tested sub-counts are compared, or what threshold constitutes sufficiency; with no output schema, this burden falls entirely on the description and is not met.

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 compact clauses with the operation front-loaded and the decision goal second; little waste. The ironic cost is that terseness drives under-specification rather than verbosity.

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 5-required-parameter analytical check with no output schema, the agent learns the input semantics from the schema but not the return shape or the sufficiency criterion. The definition is minimally viable but leaves the outcome interpretation implicit.

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 each of the five parameters (upper/lower totals and confirmed counts, plus the assignment boolean) individually documented in German. The description adds no meaning beyond that, so the baseline 3 applies.

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 does state a resource and operation (checked parts vs unchecked positions by rack zone, plus a coverage sufficiency check), but the phrasing reads like an instruction ('trennen') and the tool name suffix 'minimum' is never explained. With ~30 similarly named heating-laundry siblings, an agent cannot reliably distinguish this tool from, e.g., 'heizwaesche_zeitgleiche_ladetiefen_teilvergleich' based on this text 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?

The second clause ('whether observed zone coverage is sufficient for a load-wide conclusion') implies the decision context in which the tool applies, which is more than nothing. However, there is no explicit when-to-use/when-not guidance, no prerequisite, and no named alternative among the many sibling checks.

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