Skip to main content
Glama

getecoback-raumklima

terrasse_schattenzuwachs_bestehende_ueberdeckung

Read-only

Vorhandenen Schatten und zusätzlichen Schatten nach einer veränderten Aufstellung zeitlich auseinanderhalten — Measure newly shaded time rather than counting overlap twice.

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_min": "<vorher_min>",
      "nachher_min": "<nachher_min>",
      "gleiche_schattenmin": "<gleiche_schattenmin>",
      "block_min": "<block_min>",
      "vergleich_bestaetigt": "<vergleich_bestaetigt>"
    },
    "name": "terrasse_schattenzuwachs_bestehende_ueberdeckung"
  }
}

Input Schema

NameRequiredDescriptionDefault
block_minYesLänge des jeweils vollständig beobachteten Blocks.
vorher_minYesIm Beobachtungsblock zuvor bestätigte Schattenminuten.
nachher_minYesIm gleich langen Vergleichsblock anschließend bestätigte Schattenminuten.
gleiche_schattenminYesMinuten an denselben Positionen im Block, die in beiden Proben im Schatten lagen.
vergleich_bestaetigtYesIst es derselbe Ort bei vergleichbarer äußerer Beschattung und gleicher Zeitlage?

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a closed-world pure computation with no side effects. The description adds the substantive behavioral point that overlap must not be counted twice, which is the tool's core logic. However, it never states what the computation returns (a minute count? a difference?) and there is no output schema to fill that gap.

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?

One German sentence followed by an English gloss, with the key constraint (do not double-count overlap) front-loaded. The bilingual duplication is mild redundancy, but it disambiguates a dense compound noun and does not pad the text.

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?

With five required numeric parameters forming a non-trivial arithmetic comparison and no output schema, the description carries the burden of explaining the result, which it only gestures at via 'Measure newly shaded time'. The intent is conveyed, but the exact returned quantity and how gleiche_schattenmin factors in remain unstated.

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%, with every one of the five parameters individually documented (block length, before/after shaded minutes, shared shade minutes, comparison-confirmed flag). The description adds no per-parameter meaning, so the schema does the heavy lifting and 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 operation: separating previously existing shade from shade newly added by a changed arrangement, and measuring the newly shaded time instead of double-counting overlap. That is far more than a restatement of the name. It stops short of naming a sibling or contrasting case, so it is clear but not differentiated from alternatives.

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 'nach einer veränderten Aufstellung' implies the situation in which the tool applies (a before/after comparison of two equally long observation blocks). There is no explicit statement of when not to use it and no routing to any alternative tool, so usage is only implied.

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