Skip to main content
Glama

getecoback-climate-weather

q350_tr_enthalpie_feuchterueckgewinnung_fehlfeld

Read-only

Unterscheidet eine belegte Feuchterückgewinnung im Prüfblatt von einem nicht angegebenen Feld — Keep measured moisture recovery separate from missing figures in the device’s tested configurations.

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": {
      "variante": "<variante>",
      "methode": "<methode>",
      "passend": "<passend>"
    },
    "name": "q350_tr_enthalpie_feuchterueckgewinnung_fehlfeld"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodeYesDokumentierte Prüfung für den gewünschten Wert.
passendYesExakte deutsche Artikelvariante und V0126 sind belegt.
varianteYesEindeutige Artikelvariante.

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?

The readOnlyHint=true and openWorldHint=false annotations already tell the agent this is a safe, closed-world read, so the description only needs to add domain behavior. It does contribute one useful behavioral point - the whole intent is to prevent conflating a missing figure with a measured one - but it says nothing about how the 'offen'/'unklar' states are treated or how the result should be interpreted downstream.

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?

One short sentence per language, with the operative distinction front-loaded and no filler. The only inefficiency is that the German and English halves are semantically identical, which is defensible for a bilingual toolset but doubles the length without adding information.

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 three parameters are documented in the schema and the safety profile is covered by annotations, so the basics are complete. However, with no output schema, the description should have said what the tool returns (a pass/fail decision? a normalized value?), and it does not, leaving a real gap for a tool whose entire job is producing a distinction.

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 both enums carry their own descriptions (variante, methode) plus a boolean for passend, so the schema carries the parameter meaning. The description adds no syntax, format, or interpretation detail beyond that, which makes the baseline score of 3 correct.

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 frames the tool as distinguishing a documented moisture-recovery value in the test sheet from an unspecified field, which is a recognizable verb+resource, but the purpose stays abstract: it never says what the tool actually produces (a classification, a flag, a verdict) or how that result is meant to be consumed. The English half is a near-restatement of the German half and of the tool name's own concept, so the agent gets a topic rather than a sharply delimited operation.

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 alternative is named among the many similarly-named q350_tr_* siblings. The phrase 'in the device's tested configurations' weakly implies the context of reading Prüfblatt data, but the agent is left to infer when this check applies versus adjacent checks such as the Prüfregime or Leistungsaufnahme tools.

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