Skip to main content
Glama

getecoback-raumklima

fensterabdichtung_klebeband_oberflaeche_temperaturbeleg

Read-only

Gleiche die Klebebandangabe mit der gemessenen Rahmenoberfläche statt der Luft ab — Match a seal-tape rating to the measured frame surface, not air temperature

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": {
      "rahmen_spitze_c": "<rahmen_spitze_c>",
      "luft_spitze_c": "<luft_spitze_c>",
      "bandgrenze_c": "<bandgrenze_c>",
      "temperaturbezug": "<temperaturbezug>"
    },
    "name": "fensterabdichtung_klebeband_oberflaeche_temperaturbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
bandgrenze_cYesFür das konkrete Klebeband dokumentierte obere Betriebstemperatur
luft_spitze_cYesZeitgleich erfasste Lufttemperatur in °C
rahmen_spitze_cYesGemessene maximale Oberflächentemperatur an der Klebestelle in °C
temperaturbezugYesExplizite Bezugsgröße der Angabe

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, so the safety profile is covered. The description adds one genuinely useful behavioral fact — the comparison basis is the measured frame surface, not air — but says nothing about what the result represents (pass/fail verdict, margin, or record) or how the "temperaturbezug" enum changes the evaluation.

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 compact sentence pair with the operative constraint (surface, not air) front-loaded. The bilingual restatement is redundant for a purely German-speaking agent but doubles as clarification, and no filler or hedging is present.

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 four-required-parameter read-only check with full schema coverage, the definition covers inputs adequately, and no output schema exists to be explained. However, the tool name implies a proof/record ("beleg") and the description never indicates what the returned comparison looks like, leaving an agent guessing at the outcome shape.

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%, so all four parameters are already documented, including the enum values for temperaturbezug. The description does add orientation by telling the agent that rahmen_spitze_c rather than luft_spitze_c is the operative quantity, but it does not explain how bandgrenze_c and temperaturbezug interact in the match, so the baseline 3 applies.

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?

"Gleiche die Klebebandangabe mit der gemessenen Rahmenoberfläche ... ab" states a specific verb (match/compare) and both operands (tape rating, measured frame surface temperature). The trailing "statt der Luft" explicitly separates it from an air-temperature comparison, which is the main ambiguity an agent would face. It does not name a sibling tool, but the reference-basis distinction is clear enough to act on.

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 phrase "statt der Luft" implies when this tool is the right one (surface-referenced tape check rather than air-referenced), but there is no explicit when-to-use or when-not-to-use statement and no named alternative among the many fensterabdichtung siblings. Usage is inferable rather than stated.

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