Skip to main content
Glama

getecoback-climate-weather

sonnenschutz_geteilte_scheiben_schattenanteil

Read-only

Gewichtet beobachtete Schattenflächen nach den tatsächlichen Flächen zweier ungleich großer Scheiben — Calculate area-weighted observed shade across two unequal panes.

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": {
      "scheibe_a_m2": "<scheibe_a_m2>",
      "scheibe_b_m2": "<scheibe_b_m2>",
      "schatten_a_prozent": "<schatten_a_prozent>",
      "schatten_b_prozent": "<schatten_b_prozent>"
    },
    "name": "sonnenschutz_geteilte_scheiben_schattenanteil"
  }
}

Input Schema

NameRequiredDescriptionDefault
scheibe_a_m2YesSichtbare Fläche der ersten Scheibe in m².
scheibe_b_m2YesSichtbare Fläche der zweiten Scheibe in m².
schatten_a_prozentYesGeschätzter Anteil im sichtbaren Schatten, Scheibe A.
schatten_b_prozentYesGeschätzter Anteil im sichtbaren Schatten, Scheibe B zur selben Zeit.

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 safety profile is covered. The description adds that the aggregation is weighted by actual pane area, which is genuine behavioral context, but it says nothing about what the returned value is (percentage vs. area) or how the inputs are combined.

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 core statement is front-loaded and compact, and the verb-plus-scope formulation is clear. The sentence is however given twice (German and English), which is redundant for an agent rather than harmful, keeping it short of a 5.

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 pure four-parameter calculator with annotations covering safety and no output schema, the definition covers the essentials but leaves the shape of the result unspecified. An agent knows what goes in, not what comes out or in which unit.

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 four parameters are already documented with units and ranges, which sets the baseline at 3. The description adds only the notion that the areas act as weights for the percentages, a marginal but real clarification 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?

States a specific operation (area-weighted aggregation of observed shade) and a specific resource (two panes of unequal size), so an agent can tell it apart from a simple shade reading. It does not name or contrast any sibling such as sonnenschutz_geteiltes_fenster_minutenquote, which keeps it below a 5.

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 phrase 'zweier ungleich großer Scheiben' implicitly signals the applicable situation (two panes of different area), which is a usable usage cue. There is no explicit when-to-use/when-not statement and no pointer to an alternative for equal panes or for a time-quota-based measure.

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