Skip to main content
Glama

getecoback-raumklima

klima_aussenteil_stellplatz_check

Read-only

Einen vorgesehenen Außenstellplatz vor dem Kauf eines mobilen Splitgeräts prüfen — Check planning prerequisites for a portable split AC outdoor unit.

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": {
      "aussenplatz": "<aussenplatz>",
      "montage_bestaetigt": "<montage_bestaetigt>",
      "eigentuemer_freigabe": "<eigentuemer_freigabe>"
    },
    "name": "klima_aussenteil_stellplatz_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
aussenplatzYesEin fester, vom Hersteller vorgesehener, im Freien liegender Standort ist vorhanden?
montage_bestaetigtYesBefestigung, Abstände und Leitungsweg sind nach Herstelleranleitung am Standort geprüft?
eigentuemer_freigabeYesFreigabe für den konkreten Ort, sofern erforderlich.

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 only that this is a pre-purchase planning check; it does not say what the verdict looks like (e.g. blocking vs. advisory), how the three inputs combine, or what happens on a failing prerequisite, and there is no output schema to fill that gap.

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?

Two short, front-loaded clauses with the core action first. The German/English duplication is mildly redundant but does not bloat the definition or bury the key 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 prerequisite check with three richly documented parameters, the definition is usable, but with no output schema the description should have indicated what kind of result is produced (pass/fail, list of unmet prerequisites) and whether it blocks a purchase decision.

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%: each of the three required parameters, including the four-value enum for eigentuemer_freigabe, is documented in the schema. The description adds no additional meaning about how these inputs should be assessed, so the baseline 3 applies.

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üfen/check) and a specific resource (vorgesehener Außenstellplatz for a mobile split unit), plus the lifecycle timing (vor dem Kauf). That is concrete enough to separate it from the maintenance/measurement siblings, though it never names an alternative check by contrast.

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 'vor dem Kauf eines mobilen Splitgeräts' implies the usage window — a pre-purchase planning gate — but there is no explicit when-not guidance, no prerequisites, and no routing to a sibling such as geraet_wahl or klima_abluftweg_pruefen.

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