Skip to main content
Glama

getecoback-raumklima

klimaanlage_wechselort_fensterkit_rueckbau

Read-only

Ein mobiles Klimagerät für zwei vorbereitete Fensterorte auf verbleibende Umrüstteile prüfen — Find missing reusable fittings before moving an existing portable AC.

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": {
      "a_vollstaendig": "<a_vollstaendig>",
      "b_vollstaendig": "<b_vollstaendig>",
      "adapter_wechselbar": "<adapter_wechselbar>",
      "abdichtung_wechselbar": "<abdichtung_wechselbar>",
      "a_muss_nutzbar_bleiben": "<a_muss_nutzbar_bleiben>"
    },
    "name": "klimaanlage_wechselort_fensterkit_rueckbau"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_vollstaendigYesSind Abführung und zugelassene Fensterlösung am ersten Ort vollständig erprobt?
b_vollstaendigYesSind beide Teile auch am zweiten Ort vollständig erprobt?
adapter_wechselbarYesKann genau der vorhandene Adapter dokumentiert an beiden Orten verwendet werden?
abdichtung_wechselbarYesPasst dieselbe vorhandene Abdichtung nach Prüfung an beide Fenster?
a_muss_nutzbar_bleibenYesSoll der erste Ort auch während des zweiten Einsatzes vollständig vorbereitet bleiben?

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?

The readOnlyHint=true and openWorldHint=false annotations already declare the safety profile, and the description is consistent with a non-mutating inspection. Beyond that, it only gives the pre-move purpose; it does not explain how the five boolean conditions are evaluated or what the check returns, which matters because there is no output schema.

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 German clause is front-loaded with the action and target, and the English clause directly restates it. The bilingual duplication is mild redundancy, but the definition remains short and readable.

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?

Annotations cover read-only safety and the schema fully documents five required booleans, but the description leaves important gaps: it never says what output the check produces or how the boolean inputs combine into a result. For a tool with no output schema, that prevents a fully complete definition.

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 coverage is 100% with detailed German descriptions for each boolean, so the schema carries the parameter meaning. The description adds only broad context ('zwei vorbereitete Fensterorte', 'verbleibende Umrüstteile') and does not explain the semantics of adapter/seal reusability or the 'A must remain usable' constraint 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?

States a specific check of a mobile AC across two prepared window locations for remaining retrofit parts, which is more than a tautology. It does not clearly differentiate from sibling checks or say whether the output is a verdict, a list of missing parts, or an assessment.

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?

Explicitly frames the tool as a pre-move check ('before moving an existing portable AC'), so the agent gets a clear usage context. It does not state when not to use it or name related alternatives.

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