Skip to main content
Glama

getecoback-climate-weather

klima_service_lose_teile_uebergabe

Read-only

Vom Service bestätigte Zubehörteile einer bestehenden Klimageräteübergabe zuordnen — Decide which loose accessory categories still need explicit handover clarification.

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": {
      "auftrag_zubehoer": "<auftrag_zubehoer>",
      "schlauch_liste": "<schlauch_liste>",
      "adapter_liste": "<adapter_liste>",
      "nur_lose_teile": "<nur_lose_teile>"
    },
    "name": "klima_service_lose_teile_uebergabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
adapter_listeYesAdapter in der schriftlichen Liste aufgeführt?
nur_lose_teileYesSämtliches betrachtetes Zubehör bereits lose, ohne Arbeiten am Gerät?
schlauch_listeYesSchlauch in der schriftlichen Liste aufgeführt?
auftrag_zubehoerYesWas hat der Service zur Mitgabe schriftlich genannt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 safety and scope are covered structurally. The description contributes that the tool works against already service-confirmed parts on an existing handover, which is useful context, but it does not disclose what the decision output looks like or how the four inputs combine into a verdict — a real gap since no output schema exists.

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?

Two short clauses, so there is little waste, but the bilingual duplication restates the same idea in German and English rather than adding information. The text is not structured around the decision logic the tool actually implements.

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 four-required-parameter read-only classification tool with no output schema, the description should convey the shape of the result and the rule being applied; it conveys neither. The annotations handle safety and the schema handles inputs, so the definition is not broken, but the decision semantics remain underspecified.

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 each of the four parameters carries its own German explanation plus an enum for auftrag_zubehoer, so the baseline is 3. The description's phrases ('vom Service bestätigte Zubehörteile', 'lose Teile') loosely echo auftrag_zubehoer and nur_lose_teile but add no interpretation of how they interact.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gestures at a specific domain action ('Zubehörteile einer bestehenden Klimageräteübergabe zuordnen') and adds an English gloss narrowing it to deciding which loose accessory categories need handover clarification. However, 'zuordnen' (assign) and 'decide which need clarification' point in different directions, and nothing distinguishes this from the many other klima_service_* siblings. The agent knows the topic area but not precisely what operation is performed.

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 statement of when this tool should be used, when it should not, or which sibling to use instead for a related handover question. The phrase 'einer bestehenden Klimageräteübergabe' implies a precondition but is not framed as guidance, leaving the agent to infer applicability from the name alone.

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