Skip to main content
Glama

getecoback-raumklima

verschattung_erholung_innerhalb_eigener_streubreite

Read-only

Prüfe, ob sich der beschattete Nutzplatz wieder dem dokumentierten Ausgangsband genähert hat — Assess recovery toward the recorded baseline range after shading

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": {
      "basis_unten_c": "<basis_unten_c>",
      "basis_oben_c": "<basis_oben_c>",
      "wert_kurz_c": "<wert_kurz_c>",
      "wert_spaet_c": "<wert_spaet_c>",
      "gleicher_ort_und_aufbau": "<gleicher_ort_und_aufbau>"
    },
    "name": "verschattung_erholung_innerhalb_eigener_streubreite"
  }
}

Input Schema

NameRequiredDescriptionDefault
wert_kurz_cYesErste spätere Raumtemperatur nach Änderung der Beschattung
basis_oben_cYesObere Grenze der vorher beobachteten Temperaturspanne
wert_spaet_cYesZweite spätere Temperatur nach Änderung der Beschattung
basis_unten_cYesUntere Grenze der vorher beobachteten Temperaturspanne am selben Ort
gleicher_ort_und_aufbauYesMessort unverändert, späterer Aufbau unverändert und dokumentiert

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?

The annotations already establish a read-only, closed-world operation, and the description adds that the check compares against a documented baseline range after a shading change. It does not explain the decision criterion, threshold logic, or what kind of result is returned when values are still outside the baseline.

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?

The definition is short, front-loaded, and states the check before its qualifying context. The bilingual repetition adds some length, but no sentence is genuinely wasteful.

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 read-only check with five fully documented required parameters, the description gives enough context to understand the intended comparison. It remains incomplete because it does not describe the nature of the assessment result, especially since there is no output schema.

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 five parameters are already documented in the input schema. The description adds conceptual context about the baseline range but does not clarify any parameter meaning beyond what the schema provides.

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?

The description states a specific check — whether the shaded usable area has approached the recorded baseline range after shading — with a clear verb ('Prüfe/Assess') and resource ('recovery toward baseline'). It does not explicitly differentiate this from any sibling tool, so it stops short of a 5.

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 implied by 'after shading' and 'recorded baseline range', making it clear this is a post-change recovery check. However, there is no explicit when-to-use/when-not-to-use guidance and no named alternative for related shading or recovery assessments.

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