Skip to main content
Glama

getecoback-climate-weather

luftkuehler_lokale_probe_kaufbedarf

Read-only

Leitet den nächsten Prüfschritt aus Bedarf und beobachteten vorhandenen Optionen ab — Choose the next test or a no-buy decision from an observed local cooling need.

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": {
      "ziel": "<ziel>",
      "vorhanden_trocken_reicht": "<vorhanden_trocken_reicht>",
      "nassprobe_geeignet": "<nassprobe_geeignet>"
    },
    "name": "luftkuehler_lokale_probe_kaufbedarf"
  }
}

Input Schema

NameRequiredDescriptionDefault
zielYesGesuchte Wirkung.
nassprobe_geeignetYesVergleichbare Nassprobe mit lokalem Nutzen und akzeptiertem Raumfeuchteverlauf.
vorhanden_trocken_reichtYesBestandener örtlicher Test mit vorhandenem Luftstrom.

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, and the description is consistent with a pure decision helper. It adds the important framing that the tool outputs a decision (next test vs. no-buy) rather than a measurement, but says nothing about the shape of that decision or whether the inputs are consumed as exhausted state; with no output schema, that is a real gap.

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?

Front-loaded with the verb phrase, but the German sentence and its English gloss are near-duplicates, so half the text is translation overhead rather than new information. Short overall, yet not every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-enum, read-only decision tool with a 100%-covered schema, the description supplies the essential intent and the outcome space (test vs. no-buy). The one meaningful omission is what the returned decision looks like, which no output schema covers.

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% with three fully described enums, so the schema carries the parameter meaning. The description gestures at 'Bedarf' and 'beobachteten vorhandenen Optionen', which loosely maps to ziel and vorhanden_trocken_reicht, but adds no interpretation of the enum values or how conflicting/open states are resolved.

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?

States a specific action (derive the next Prüfschritt / test-or-no-buy decision) rather than restating the name, and the German/English pair makes the intent unambiguous: this is the meta decision step over an observed cooling need. It does not name or contrast against the many sibling *_probe tools, so the agent must infer that this is the routing layer rather than another measurement.

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?

Implies the usage context (an observed local cooling need plus already-observed options) and mentions the no-buy outcome, but gives no explicit when-not guidance and never says how this differs from invoking a concrete probe sibling directly. Adequate but leaves the selection decision to inference.

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