Skip to main content
Glama

getecoback-raumklima

luftkuehler_trockenkontrolle_restfeuchte_beleg

Read-only

Prüft ob der Referenzlauf als trockene Probe dokumentiert ist — Check whether a fan-only control was actually documented as dry.

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": {
      "modus_hersteller": "<modus_hersteller>",
      "wasserzufuhr": "<wasserzufuhr>",
      "matte": "<matte>"
    },
    "name": "luftkuehler_trockenkontrolle_restfeuchte_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
matteYesZuvor dokumentierter Zustand der Matte.
wasserzufuhrYesZustand vor Beginn der Probe.
modus_herstellerYesDokumentierter Betrieb.

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 safety is covered. The description adds that the check is about whether a documented reference run counts as dry, but it never says how 'unbekannt'/'trocken_nicht_belegt' inputs are treated or what verdict shape comes back, which matters because there is no output schema.

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?

A single front-loaded sentence with no filler; the bilingual duplication is redundant for a reader fluent in either language but is not wasteful enough to obscure the purpose.

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?

Read-only check with fully documented parameters, but no output schema and no described result, so the description leaves the agent unable to predict what a passing or failing check returns. Given the tool is purely a verification, that gap is meaningful though not fatal.

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 coverage is 100% and all three enums carry their own descriptions, so the schema does the heavy lifting. The description adds no extra meaning about how matte, wasserzufuhr, and modus_hersteller combine into a verdict.

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?

Uses a specific verb ('Prüft') plus a specific subject ('ob der Referenzlauf als trockene Probe dokumentiert ist'), and the English gloss clarifies the intended semantics of 'fan-only control'. It does not, however, distinguish this from nearby moisture/evidence checks such as luftkuehler_alternierende_nassphasen_sitzzeit or luftkuehler_betriebswechsel_pumpe_luft_getrennte_belege.

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?

No statement of when to call this versus the many sibling evidence tools, no preconditions, and no exclusions. The agent must infer the trigger condition entirely from the tool name and schema enums.

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