Skip to main content
Glama

getecoback-climate-weather

btu_empfehlung

Überschlägige Kühlleistung (BTU/h) aus Raumfläche und Sonne. — Estimate cooling capacity in BTU/h from room area and sun exposure, using the website's baseline of 340 BTU/h per m². Consider a detailed load calculation for large rooms.

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": {
      "qm": "<qm>"
    },
    "name": "btu_empfehlung"
  }
}

Input Schema

NameRequiredDescriptionDefault
qmYesRaumfläche in m² — room floor area in square metres (4–120)
sonneNoSonneneinstrahlung — sun exposure: wenig = low/shaded, normal, viel = strong (south/west or top floor). Default: normal

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / qm / description
      Previous value: -"Raumfläche in m² (4–120)"New value: +"Raumfläche in m² — room floor area in square metres (4–120)"
    • changedInput schema / properties / sonne / description
      Previous value: -"Sonneneinstrahlung des Raums (Default: normal)"New value: +"Sonneneinstrahlung — sun exposure: wenig = low/shaded, normal, viel = strong (south/west or top floor). Default: normal"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does disclose meaningful behavior: the calculation baseline of 340 BTU/h per m², and the accuracy limitation requiring a proper load calculation for large rooms. It stops short of stating that the tool is a pure, side-effect-free computation or how the result is returned (though no output schema exists).

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 sentences, front-loaded with the purpose, and the caveat is placed last where it belongs. The German and English sentences duplicate the same content, which costs a little space but follows a consistent bilingual convention.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter calculator with full schema coverage and no output schema, the description covers purpose, method, and accuracy limits adequately. The only minor omission is any hint about the shape or rounding of the returned BTU value.

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%: qm's range (4–120 m²) and sonne's enum values with their meanings and default are all documented in the schema. The description only restates that area and sun drive the estimate, adding no syntax or weighting detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a specific verb ('Estimate') with a specific resource and unit ('cooling capacity in BTU/h') and names the two inputs (room area, sun exposure). It also discloses the method's basis (340 BTU/h per m²), so an agent knows exactly what this tool produces without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It signals the tool's scope as a rough ('überschlägig') estimate and explicitly warns off large rooms in favor of a detailed load calculation. It gives clear context for use but names no concrete alternative tool, and the threshold for 'large' is left qualitative.

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