Skip to main content
Glama

getecoback-climate-weather

punktwaerme_abschattung_referenzgain

Read-only

Die Änderung am abgeschatteten Arbeitsplatz in Relation zur separat protokollierten freien Sicht einordnen — Compare two measured local surface gains after subtracting their respective start readings.

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": {
      "start_frei_c": "<start_frei_c>",
      "ende_frei_c": "<ende_frei_c>",
      "start_schatten_c": "<start_schatten_c>",
      "ende_schatten_c": "<ende_schatten_c>",
      "vergleich_bestaetigt": "<vergleich_bestaetigt>"
    },
    "name": "punktwaerme_abschattung_referenzgain"
  }
}

Input Schema

NameRequiredDescriptionDefault
ende_frei_cYesEndwert dieser Fläche beim freien Lauf.
start_frei_cYesAnfangswert derselben Messfläche beim bereits zulässig beobachteten Lauf ohne Abschattung.
ende_schatten_cYesEndwert derselben Fläche bei der Abschattung.
start_schatten_cYesAnfangswert beim separaten Lauf mit beobachteter Abschattung.
vergleich_bestaetigtYesGleiches Messmaterial, gleiche Laufdauer, sonstige Randbedingungen und bestätigte Konfiguration?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already state readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds meaningful behavioral detail by specifying that each surface's gain is computed by subtracting its respective start reading before comparison, which is beyond what the annotations provide.

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 and front-loads the core comparison purpose. The German and English sentences are largely redundant translations, which is mild waste, but the content remains efficient and easy to parse.

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 computation tool with five fully described required parameters, the description explains the inputs and the subtraction logic adequately. However, there is no output schema, and the description does not say what the comparison returns (e.g., a difference, ratio, or qualitative assessment), leaving a meaningful 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 the parameter meanings are already fully documented in the schema. The description reinforces that the start values are subtracted from the end values to obtain gains, but it does not add syntax, units, or other details beyond the schema.

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 uses a specific verb ('einordnen'/'Compare') and identifies the resource: two measured local surface gains, one at a shadowed workplace and one from a separate free-view measurement. It is clear what the tool does, but it does not explicitly differentiate itself from any sibling 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?

The description implies when to use it — when you have two measured surface gains and want to compare them after subtracting start readings. It gives no explicit when-not guidance, prerequisites, or named alternatives among the many sibling tools.

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