Skip to main content
Glama

getecoback-climate-weather

haushaltsklima_wechselereignisse_eindeutiger_vorlauf

Read-only

Ordne eine beobachtete Änderung einem eindeutigen vorausgehenden Eingriff zu, wenn kein zweiter überlappt — Scope an observed response to one preceding intervention when another cannot overlap

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": {
      "beschattung_min": "<beschattung_min>",
      "lueftung_min": "<lueftung_min>",
      "messung_min": "<messung_min>",
      "zeitaufloesung_min": "<zeitaufloesung_min>"
    },
    "name": "haushaltsklima_wechselereignisse_eindeutiger_vorlauf"
  }
}

Input Schema

NameRequiredDescriptionDefault
messung_minYesMinute der ersten beobachteten Änderung, gleiche Zeitskala
lueftung_minYesMinute der Öffnung
beschattung_minYesMinute des Verschattens
zeitaufloesung_minYesUnsicherheitsabstand um dokumentierte Ereigniszeiten

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 uniqueness/overlap constraint but does not say what happens if no unique predecessor exists, whether the result can be null, or how ties are handled.

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 front-loaded and reasonably short, but the German sentence is immediately repeated in English, making it longer than necessary. The duplication may aid bilingual readers but does not add new information.

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 read-only tool with four fully documented required parameters and no output schema, the definition covers the main purpose and condition. It remains incomplete about ambiguous cases, return behavior, and what happens when the uniqueness condition fails.

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 required numeric parameters are already documented in the schema. The description adds conceptual framing around the observed change and preceding intervention but does not add syntax, units, or constraints 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?

The description names a specific operation: assigning an observed change to a unique preceding intervention when no second intervention overlaps. It is clear enough to distinguish the core task, but it does not explicitly contrast itself with any sibling tool or clarify the meaning of 'eindeutig' in ambiguous cases.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear usage condition: apply when no second intervention overlaps, so the preceding intervention is unique. It does not state what to do when multiple interventions overlap or name an alternative tool, but the primary context for use is explicit.

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