Skip to main content
Glama

getecoback-raumklima

sonnenschutz_scheibe_und_platz_reagieren_getrennt

Read-only

Trenne bei einer Beschattungsprobe die Reaktion der Scheibe von der Reaktion der Raumluft am Nutzplatz — Separate glass and occupied-zone response 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": {
      "scheibe_vor_c": "<scheibe_vor_c>",
      "scheibe_nach_c": "<scheibe_nach_c>",
      "platz_vor_c": "<platz_vor_c>",
      "platz_nach_c": "<platz_nach_c>",
      "luftmess_toleranz_c": "<luftmess_toleranz_c>",
      "messpaare_passend": "<messpaare_passend>"
    },
    "name": "sonnenschutz_scheibe_und_platz_reagieren_getrennt"
  }
}

Input Schema

NameRequiredDescriptionDefault
platz_vor_cYesGleichzeitiger Luftwert vor Beschattung am Nutzplatz
platz_nach_cYesGleichzeitiger Luftwert nach Beschattung am Nutzplatz
scheibe_vor_cYesVorher am selben Scheibenpunkt bestimmt
scheibe_nach_cYesNachher am gleichen Scheibenpunkt
messpaare_passendYesZeitpaare und Umgebung dokumentiert, kein Wechsel von Sensorort oder Messart
luftmess_toleranz_cYesToleranz für eine Änderung des Raumluftwerts

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 readOnlyHint and openWorldHint annotations already establish that this is a safe, local read/computation. The description adds that the tool separates glass and occupied-zone responses, but it does not explain the returned result, how tolerance is applied, or what happens when messpaare_passend is false.

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 a single front-loaded sentence with no filler, stating the operation before the English gloss. The bilingual repetition is slightly longer than necessary but remains efficient and clear.

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?

The input schema is fully described, but there is no output schema and the description does not say what the separated responses look like or how the messpaare_passend gate affects execution. For a six-required-parameter analytical tool, that leaves a meaningful completeness gap.

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 six parameters are already well documented. The description reinforces the conceptual grouping of glass versus occupied-zone measurements, but adds no parameter-level detail 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 names a specific operation ("Trenne") and two concrete resources (glass response and occupied-zone air response) within a shading test. It is clear enough to distinguish from sibling shading tools by its focus on separating the two responses, though it does not explicitly name an alternative tool.

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 "bei einer Beschattungsprobe" supplies an implied usage context, so the agent can infer this is for post-shading comparison measurements. However, there are no explicit when-not conditions, prerequisites, or named alternatives among the many shading-related siblings.

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