Skip to main content
Glama

getecoback-climate-weather

infrarotheizung_leihe_vor_ankauf_nachprobe

Read-only

Befunde einer Arbeitsplatzprobe auf zwei andere Sitzsituationen nur bei passenden Randbedingungen übertragen — Flag when seat trials cannot transfer to other use cases.

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": {
      "a_erprobt": "<a_erprobt>",
      "b_distanc_und_sicht": "<b_distanc_und_sicht>",
      "c_distanc_und_sicht": "<c_distanc_und_sicht>",
      "b_nutzung_vergleichbar": "<b_nutzung_vergleichbar>",
      "c_nutzung_vergleichbar": "<c_nutzung_vergleichbar>",
      "geraet_stellung_freigegeben": "<geraet_stellung_freigegeben>"
    },
    "name": "infrarotheizung_leihe_vor_ankauf_nachprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_erprobtYesWar die Wärme am Referenz-Sitzplatz bei der tatsächlichen Anwendung passend?
b_distanc_und_sichtYesStimmen Abstand, freie Sicht und Ausrichtung an B mit der Probe überein?
c_distanc_und_sichtYesStimmen Abstand, freie Sicht und Ausrichtung an C überein?
b_nutzung_vergleichbarYesSind Aufenthaltsdauer, Kleidung und Ausgangslage B vergleichbar?
c_nutzung_vergleichbarYesSind Aufenthaltsdauer, Kleidung und Ausgangslage C vergleichbar?
geraet_stellung_freigegebenYesPassen dokumentierte Gerätevorgaben bei allen betrachteten Stellorten?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. Beyond that the description discloses the decision rule (transfer only if boundary conditions match), which is genuine context, but it says nothing about the form of the result, whether all six conditions act as a hard AND-gate, or which conditions are typically the blockers.

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 description is short and the constraint is front-loaded, but it is written twice — a German sentence followed by an English gloss that restates the same idea — so roughly half the text is redundant. The mixed-language phrasing also makes it slower to parse for an agent keying on one language.

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 six-required-boolean gate with full schema coverage, no output schema and read-only annotations, the essentials are present, but the agent is left without the domain anchor (infrared heater loan before purchase) and without knowing whether the response is a single verdict or a list of failing conditions. Those are the two facts needed to use the result correctly.

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 each boolean carries its own German question, so the schema does the heavy lifting; the baseline of 3 applies. The description corroborates the B/C pairing and the 'Randbedingungen' framing but omits geraet_stellung_freigegeben (documented device positioning) and adds no semantics about how the booleans combine into a verdict.

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 German clause names a specific action (transferring workplace-trial findings to two other seating situations only under matching boundary conditions) and the English adds the decision framing (flag when transfer is not possible). However, the description never mentions the domain implied by the tool name (Infrarotheizung/Leihe/vor Ankauf), so an agent cannot connect this gate to the heater-loan-purchase workflow from the description alone. It also gives no differentiation from the many sibling *_vor_* check tools.

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 is only implicit: the phrase 'nur bei passenden Randbedingungen übertragen' signals that this check applies when a trial result is being extended to other seat positions. There is no explicit when-to-use/when-not statement, no mention of what to do with a negative flag, and no named alternative among the siblings. An agent can infer the context but must reconstruct it.

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