Skip to main content
Glama

getecoback-climate-weather

innenbehang_lueftung_licht_bedienprobe

Read-only

Findet beobachtete Behangstellungen, in denen Fensterbedienung und eigenes Lichtziel zugleich möglich waren — Identify shade positions that met window operation and light preferences in the same observation.

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": {
      "oben": "<oben>",
      "mitte": "<mitte>",
      "unten": "<unten>"
    },
    "name": "innenbehang_lueftung_licht_bedienprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
obenYesBefund mit hochgezogenem Behang.
mitteYesBefund mit teilweise geschlossenem Behang.
untenYesBefund mit vollständig geschlossenem Behang.

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 by structured data. The description adds the substantive evaluation rule (both conditions must hold within one observation), which is real behavioral context, but it never says what the call returns, how the three positional findings combine, or how ties/none-cases are handled. With annotations carrying safety, a 3 fits.

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 a single sentence, but the entire text is presented twice, once in German and once in English, with the English half adding no new information. Front-loading is fine, yet roughly half the tokens are redundant duplication.

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, closed-world tool with three required, fully documented, enum-typed parameters and no output schema, the definition covers the criterion but not the outcome: what result shape arrives, and whether it reports positions, booleans, or a list, is unstated. Adequate but with a clear gap for correct invocation and result interpretation.

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% and all three enum parameters are documented in the schema ("Befund mit hochgezogenem Behang" etc.), so the baseline of 3 applies. The description adds nothing about the parameter semantics — notably it never explains how the enum values like "beides" or "nur_licht" map onto its stated criterion, leaving the schema to do all the work.

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 gives a specific verb ("Findet"/"Identify") and a specific resource ("beobachtete Behangstellungen" / "shade positions"), plus the exact joint criterion: window operation and own light preference satisfied in the same observation. That is concrete enough to distinguish it from generic scheduling or airflow siblings, though it offers no explicit contrast with any named alternative and leaves the input-to-output relation slightly opaque (three per-position findings in, matching positions out).

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?

There is no when-to-use guidance, no prerequisites, no exclusions, and no mention of what an agent should do instead when the criterion does not apply. The criterion itself is stated, which implies a search use case, but an agent gets no help deciding when this tool is the right call versus the many sibling evaluation tools.

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