Skip to main content
Glama

getecoback-climate-weather

fenster_teilverschattung_punktlicht_kontrast

Read-only

Berechnet den Beleuchtungsunterschied an zwei gleich gemessenen Stellen vor und nach Teilverschattung — Compare measured light-level contrast at two points before and after partial 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": {
      "vorher_hell_lux": "<vorher_hell_lux>",
      "vorher_dunkel_lux": "<vorher_dunkel_lux>",
      "nachher_hell_lux": "<nachher_hell_lux>",
      "nachher_dunkel_lux": "<nachher_dunkel_lux>",
      "aussenlicht_aehnlich": "<aussenlicht_aehnlich>"
    },
    "name": "fenster_teilverschattung_punktlicht_kontrast"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorher_hell_luxYesHeller Messpunkt vor der Änderung in lx.
nachher_hell_luxYesErster Messpunkt nach der Änderung in lx.
vorher_dunkel_luxYesZweiter Messpunkt vor der Änderung in lx.
nachher_dunkel_luxYesZweiter Messpunkt nach der Änderung in lx.
aussenlicht_aehnlichYesWaren Position, Sensorwinkel und Außenlicht bei beiden Messungen vergleichbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 safety profile is covered. The description adds that the two points must be measured identically, reinforcing the comparability condition, but it does not disclose what the calculation returns, how the aussenlicht_aehnlich=false case is handled, or any other behavior beyond the annotations.

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 bloat, but it includes a full English translation after the German, which is redundant rather than additive. The structure is clear and efficient overall.

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 five-parameter read-only calculation tool with no output schema, the description covers the core operation but omits what result is produced and how the boolean comparability flag affects the outcome. It is minimally adequate but leaves clear gaps an agent would want filled.

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 five parameters are already documented with meaning and units. The description adds only the general framing of two equally measured points, which is largely redundant with the schema's per-parameter descriptions. Baseline 3 is appropriate.

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 states a specific verb ('Berechnet' / 'Compare') and resource ('Beleuchtungsunterschied' / 'light-level contrast') scoped to two points before and after partial shading. It is clear enough to identify the operation, but it does not explicitly differentiate it from similarly named fenster_* tools such as fenster_sonneneintrag_bilanz or verschattung_blendpause_zwei_fenster_arbeit.

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

Usage Guidelines2/5

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

Usage is only implied by the phrasing 'vor und nach Teilverschattung'; there is no explicit statement of when to choose this tool, when not to, or which sibling alternative handles a different measurement scenario. The agent gets context but no routing guidance.

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