Skip to main content
Glama

getecoback-raumklima

klimaanlage_mietwohnung_unterlagencheck

Read-only

Fehlende Unterlagen für die geplante Klimaanlagen-Aufstellung in einer Mietwohnung erfassen — Identify missing model, placement and approval documents before an installation decision.

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": {
      "eingriff": "<eingriff>",
      "schriftliche_klaerung": "<schriftliche_klaerung>",
      "unterlagen": "<unterlagen>",
      "standort_skizziert": "<standort_skizziert>"
    },
    "name": "klimaanlage_mietwohnung_unterlagencheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
eingriffYesGeplanter Eingriff in Fenster, Fassade oder Bausubstanz.
unterlagenYesHerstellerunterlagen mit Aufstellungs- und Abluftweg vorhanden?
standort_skizziertYesAufstellort und betroffene Bauteile dokumentiert?
schriftliche_klaerungYesSofern ein Eingriff geplant ist: schriftliche Abstimmung für genau diese Ausführung vorhanden?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 agent knows this is a safe, locally scoped assessment. The description adds that the purpose is gap detection before a decision, but says nothing about what the agent receives back (for example a list of missing items) or how the checklist inputs are combined.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dual-language sentence with the gap-checking action front-loaded and the decision context second. No filler, no repetition of field names beyond what aids comprehension.

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?

All four required parameters are documented in the schema and the annotations cover the safety profile, so basic callability is satisfied. However, with no output schema, the description leaves the return value undefined – an agent cannot tell whether it receives a boolean verdict, a missing-items list, or prose – and the German/English split adds mild ambiguity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and each parameter already carries a German description, so the baseline is 3. The description earns a step up by mapping three of the four inputs onto recognizable concepts (model/manufacturer documents, placement site, written approval), giving the agent a mental model of the checklist rather than just field names.

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 concrete verb ('Fehlende Unterlagen ... erfassen') and a specific resource and scope (Klimaanlagen-Aufstellung in einer Mietwohnung) and lists the document classes it checks (model, placement, approval). It is clearly distinguishable from number-crunching siblings such as klimaanlage_stromkosten, though it does not explicitly contrast itself with the closest relative, bad_heizgeraet_freigabe_unterlagen.

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 only usage cue is the timing phrase 'before an installation decision', which implies this is a pre-installation gate. There is no statement of when not to use it, no prerequisite mention, and no named alternative for related document checks.

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