Skip to main content
Glama

getecoback-climate-weather

klimafenster_stoffklappe_rueckkehr_in_lage

Read-only

Bilanziert normale Zyklen bei denen eine Stoffklappe nach Ende des Luftstroms sichtbar zurückkehrte — Count observed return-to-rest cycles of an existing fabric flap.

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": {
      "gesehen": "<gesehen>",
      "zurueck": "<zurueck>",
      "selbst_gewaehltes_ziel": "<selbst_gewaehltes_ziel>"
    },
    "name": "klimafenster_stoffklappe_rueckkehr_in_lage"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesehenYesVollständig beobachtete reguläre Zyklen.
zurueckYesDavon mit Rückkehr an die Ausgangsmarke.
selbst_gewaehltes_zielYesGewünschte Zahl vollständiger, erfolgreicher Beobachtungen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish that this is a read-only, non-open-world operation, so the safety profile is covered. The description adds useful behavioral context by defining the counted event as a visible return after the end of airflow, but it does not explain the returned result, how the target parameter affects output, or any validation behavior.

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?

The description is short and front-loads the core action. The bilingual German/English rendering duplicates the same content, which is mildly wasteful, but it does not obscure the meaning.

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 three required numeric parameters and no output schema, the description is adequate but incomplete. It does not explain what the tool returns or how the desired target parameter influences the result, leaving an agent to infer the output shape.

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 already documented in the input schema. The description reinforces the domain context of the counts but does not add meaning beyond the schema, such as the relationship between observed cycles and returned cycles.

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 states a specific verb and resource: counting observed return-to-rest cycles of an existing fabric flap, with scope limited to normal cycles after airflow ends. It is clear what is being counted, but it does not explicitly distinguish this tool from similarly named klimafenster observation/measurement 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?

The description gives no when-to-use guidance, no exclusions, and no alternatives. An agent can infer that it applies when counting observed fabric-flap return cycles, but that is implied by the purpose rather than stated as usage guidance.

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