Skip to main content
Glama

getecoback-raumklima

wohnmessung_sonnenfleck_zeitmaske_ortsvergleich

Read-only

Direkte Sonne an zwei Messorten aus einem gemeinsamen Messblock herausrechnen — Mask both sensors’ direct-sun windows before comparing rooms.

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": {
      "mess_ab": "<mess_ab>",
      "mess_bis": "<mess_bis>",
      "sonne_a_ab": "<sonne_a_ab>",
      "sonne_a_bis": "<sonne_a_bis>",
      "sonne_b_ab": "<sonne_b_ab>",
      "sonne_b_bis": "<sonne_b_bis>",
      "abklingen": "<abklingen>"
    },
    "name": "wohnmessung_sonnenfleck_zeitmaske_ortsvergleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
mess_abYesBeginn des kontinuierlichen gemeinsamen Messblocks.
mess_bisYesEnde des Blocks.
abklingenYesSelbst gewählter zusätzlicher Ausschluss je Gerät nach Ende der Einstrahlung.
sonne_a_abYesBeginn der beobachteten direkten Sonne am Gerät A.
sonne_b_abYesBeginn der beobachteten direkten Sonne am Gerät B.
sonne_a_bisYesEnde am Gerät A.
sonne_b_bisYesEnde am Gerät B.

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 substantive behavior that the operation subtracts/masks sun windows from a common block, but it never says what the agent receives back — a trimmed interval set, counts, or a comparison table — which matters for a 7-parameter computation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the operation, which is good. The German sentence is immediately restated in English, which is redundant duplication rather than added information, and the em-dash construction makes the second clause read as a paraphrase instead of a distinct fact.

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 seven required parameters, no output schema, and no nested structure, the description is adequate on the input side because the schema carries full parameter documentation. It is incomplete on the outcome side: for a masking/comparison computation the agent cannot tell what is produced or how intervals are represented, so it is viable but with a clear gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and every parameter carries a German explanation of its role (block start/end, per-device sun start/end, and the self-chosen decay exclusion). The description adds a light conceptual frame — that the two sun windows belong to a shared block and are masked before comparison — but no new syntactic or range detail beyond the schema, so it sits just above the baseline 3.

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 (masking direct-sun windows at two sensors within a shared measurement block before a room comparison) rather than restating the name. The resource is concrete: the joint measurement block plus per-device sun intervals. It stops short of explicitly distinguishing itself from the other 'wohnmessung' siblings, so it lands at 4 rather than 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 'before comparing rooms' implies this is a preprocessing step that precedes a comparison, which is genuine usage context. However, there is no explicit when-to-use/when-not guidance, no naming of an alternative preprocessing or comparison tool, and no prerequisite conditions stated.

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