Skip to main content
Glama

getecoback-raumklima

terrasse_beschattung_saison_probeuhrzeit_vergleich

Read-only

Getestete Schattenzeiten zweier Jahresabschnitte gegen den gleichen geplanten Termin prüfen — Compare two observed seasonal shadow shifts at the same meeting time.

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": {
      "alt_beginn": "<alt_beginn>",
      "alt_ende": "<alt_ende>",
      "aktuell_beginn": "<aktuell_beginn>",
      "aktuell_ende": "<aktuell_ende>",
      "termin": "<termin>",
      "ort_und_aufbau_gleich": "<ort_und_aufbau_gleich>"
    },
    "name": "terrasse_beschattung_saison_probeuhrzeit_vergleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
terminYesGeplanter Besuchsbeginn, verglichen auf derselben Ortsuhrskala.
alt_endeYesBeobachtetes Ende desselben Abschnitts.
alt_beginnYesBeobachteter Beginn der Beschattung im früheren Jahresabschnitt.
aktuell_endeYesIn der jetzigen Jahreszeit beobachtetes Ende.
aktuell_beginnYesIn der jetzigen Jahreszeit beobachteter Beginn.
ort_und_aufbau_gleichYesTatsächlich gleicher Terrassenplatz und gleicher festgehaltener Aufbau?

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 the meaningful constraint that the two periods are compared against the same planned time and implicitly that observations must be comparable, but it says nothing about how mismatched or implausible inputs are handled or what the comparison concludes.

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?

A single front-loaded sentence states the comparison before the English gloss, with no filler. The German/English duplication costs a little length but aids disambiguation of an unusual compound tool name.

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?

All six required parameters are well described in the schema, but with no output schema the description never indicates what the comparison returns (a verdict, a delta, a boolean) or how a failed identity check affects the result. For a read-only six-parameter comparison tool this leaves a real gap 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 six parameters (including the same-clock-scale framing of 'termin' and the identity check 'ort_und_aufbau_gleich') are already documented in the schema. The description only restates the comparison frame rather than adding units, formats, or interpretation 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?

The description names a specific verb (compare/check) and resource (observed shading times of two seasonal periods against the same planned appointment time), which is more precise than the tool name alone. It does not, however, explicitly differentiate itself from near siblings such as terrasse_schattenfolge_pause_ohne_platzwechsel or terrasse_schattenzuwachs_bestehende_ueberdeckung, so an agent must infer the distinction.

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 phrasing 'gegen den gleichen geplanten Termin' implies the scenario (comparing an earlier season's shading window with the current one at one fixed meeting time), which is enough to infer when to use it. There is no explicit when-not guidance, no mention of prerequisites such as measurements having been taken, and no named alternative tool.

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