Skip to main content
Glama

getecoback-raumklima

fenster_sonneneintrag_bilanz

Read-only

Wärmeeintrag desselben Fensters vor und nach Verschattung vergleichen — Estimate the solar heat gain of a window with and without a shade.

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": {
      "glas_m2": "<glas_m2>",
      "sonne_w_m2": "<sonne_w_m2>",
      "g_vorher": "<g_vorher>",
      "g_nachher": "<g_nachher>"
    },
    "name": "fenster_sonneneintrag_bilanz"
  }
}

Input Schema

NameRequiredDescriptionDefault
glas_m2YesSonnenbeschienene Glasfläche in m².
g_vorherYesGesamtenergiedurchlassgrad der vorhandenen Kombination als Anteil von 0 bis 1.
g_nachherYesGesamtenergiedurchlassgrad der Verglasung mit geplanter Verschattung als Anteil von 0 bis 1.
sonne_w_m2YesEinstrahlung auf die Fensterebene in W/m².

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 safe, local, pure-computation nature is largely covered. The description reinforces this only implicitly by framing the tool as an estimate/comparison, and adds nothing about determinism, assumptions made in the calculation, or what the comparison yields conceptually.

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?

Two short sentences, front-loaded with the German statement of intent followed by the English equivalent, with no filler. The bilingual duplication is slightly redundant for an agent but aids unambiguous interpretation of the domain terms.

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 simple four-parameter, annotation-covered calculator, the description covers the what and the scenario. With no output schema, however, nothing is said about what the result looks like — a single delta value, a pair of watt figures, or a verdict — leaving the agent unable to anticipate the return shape or how to interpret it.

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%, with units (m², W/m², 0–1 fraction) and ranges documented per parameter, so the schema does the heavy lifting. The description's 'with and without a shade' phrase loosely maps to g_vorher/g_nachher but adds no interpretation or constraints beyond what the schema states.

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 concrete verb and resource: 'Wärmeeintrag desselben Fensters vor und nach Verschattung vergleichen' / 'Estimate the solar heat gain of a window with and without a shade'. It makes the operation and the before/after comparison explicit. It does not, however, name or distinguish itself from any sibling, so an agent must infer that no other tool computes solar gain comparisons.

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 implied by the 'with and without a shade' framing — that a shading option is being evaluated. There is no explicit statement of when to prefer this tool, what preconditions exist (e.g. need known g-values), or what alternative to use for related window/thermal questions among the many 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