Skip to main content
Glama

getecoback-raumklima

fenster_sonnenschutz_messreihe_wolkenwechsel

Read-only

Prüft welche Phasen einer Fensterbeschattungsprobe mit unverändertem Wolkenzustand überhaupt auswertbar waren — Identify parts of a shade measurement with consistently observed cloud cover.

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": {
      "gleich_min": "<gleich_min>",
      "geaendert_min": "<geaendert_min>",
      "unbekannt_min": "<unbekannt_min>"
    },
    "name": "fenster_sonnenschutz_messreihe_wolkenwechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
gleich_minYesMinuten mit für beide Fälle gleichartigem beobachtetem Himmel in Minuten.
geaendert_minYesMinuten mit sichtbarem Wechsel in einem der Fälle in Minuten.
unbekannt_minYesMinuten ohne Himmelbeobachtung. Gruppen dürfen sich nicht überlappen. in Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 intent (which phases are actually usable given consistent cloud cover), but it does not disclose the return shape or result granularity, and it omits the schema-level constraint that the three groups must not overlap — a behavioral rule an agent could easily violate.

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?

The description is short and front-loaded, but it is the same sentence in German and then in English, which doubles length without adding information. The structure is otherwise clean, with no tangential content.

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 no output schema, the description should say what the tool returns (counts? a list of phases? a boolean verdict?) and how the categories combine; it only gestures at 'which phases are evaluable'. For a three-required-parameter computation tool, this is minimally viable but leaves real ambiguity about the result.

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 three parameters are documented in the schema itself, and the description adds no syntax or unit detail beyond that. Baseline 3 applies; the description only loosely frames the parameters as a partitioning of observed minutes.

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 verb ('Prüft' / 'Identify') and a specific resource (the evaluable phases of a Fensterbeschattungsprobe with unchanged cloud state). An agent can tell it is an evaluability filter over minute counts rather than a measurement tool. It does not, however, differentiate itself from the many related sonnenschutz/messreihe siblings.

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?

No statement of when to call this versus the sibling tools (e.g. the minute-quote or repetition-counting tools), and no prerequisites such as needing all three minute totals to be non-overlapping and available. Usage must be inferred from the name and the schema's required fields.

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