Skip to main content
Glama

getecoback-climate-weather

bauteil_waermeverlust

Read-only

Wärmefluss durch ein bekanntes Bauteil vor und nach einer U-Wert-Änderung vergleichen — Compare steady-state transmission through one building element.

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": {
      "area_m2": "<area_m2>",
      "old_u": "<old_u>",
      "new_u": "<new_u>",
      "difference_k": "<difference_k>"
    },
    "name": "bauteil_waermeverlust"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_uYesVergleichs-U-Wert in W/(m²·K).
old_uYesBisheriger U-Wert in W/(m²·K).
area_m2YesNettofläche des Bauteils in m².
difference_kYesTemperaturdifferenz auf beiden Seiten des Bauteils in K.

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. The description contributes one genuinely useful behavioral constraint — that the calculation is steady-state — but says nothing about what the result represents (heat-flow delta in W?), assumptions about thermal bridges, or precision.

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 compact sentences with the operative verb and scope front-loaded. The German/English duplication is mild redundancy rather than waste.

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?

No output schema exists, so the description is the only place to explain what comes back; it never states the return value or its units for a computation tool. It is otherwise adequate for a four-parameter, fully-documented read-only calculation.

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% and every parameter carries units and ranges in the schema. The description adds no semantics beyond that, so the baseline of 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?

Names a concrete operation (compare heat flow through one building element before and after a U-value change) with a specific resource. The bilingual restatement ('Wärmefluss ... vergleichen — Compare steady-state transmission') adds the key qualifier 'steady-state' but does not differentiate it from any of the many sibling calculation 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?

'vor und nach einer U-Wert-Änderung' implies the retrofit/improvement scenario, so usage is inferable. There is no explicit statement of when to prefer this over other calculation siblings, nor any exclusions or prerequisites.

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