Skip to main content
Glama

getecoback-raumklima

daikin_mc80zvm_massangabe_geraet_oder_aufbau

Read-only

Liest die nackten Gerätemaße nur für den zugehörigen Zustand und lässt montierte Maße ohne eigenen Beleg offen — Keep published body dimensions separate from measured assembled dimensions.

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": {
      "gefragt": "<gefragt>",
      "mc80zvm_belegt": "<mc80zvm_belegt>",
      "messung_komplett": "<messung_komplett>"
    },
    "name": "daikin_mc80zvm_massangabe_geraet_oder_aufbau"
  }
}

Input Schema

NameRequiredDescriptionDefault
gefragtYesGesuchter Zustand.
mc80zvm_belegtYesGerät und Ausgabe der deutschen Anleitung passen.
messung_komplettYesKomplette montierte Gerätehöhe, Breite und Tiefe wurden unabhängig gemessen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The readOnlyHint annotation already establishes that this is a read operation, and the description adds the useful constraint that unproven assembled measurements are left open rather than inferred. It does not explain the return format or what concretely happens for each parameter combination.

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 definition is compact and front-loads the key separation between bare device dimensions and assembled dimensions. The German sentence is followed by an English restatement, which is slightly redundant but does not obscure the core point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With three required parameters and no output schema, the description should explain more about how the boolean inputs affect the result or what is returned when evidence is missing. It gives the governing principle but not enough operational detail for an agent to predict outcomes across the parameter combinations.

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%, so the schema already explains each parameter. The description adds the conceptual link between the requested state, published device dimensions, and the need for independent evidence for assembled dimensions, but it does not add format or enum-level detail 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?

The description names a specific operation and resource: it reads bare device dimensions only for the corresponding state. It also distinguishes published body dimensions from measured assembled dimensions, though it does not explicitly name a sibling alternative.

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 description implies that the tool should be used for device dimensions and not for assembled dimensions without independent evidence. However, it does not state explicit when-to-use/when-not-to-use rules or name an alternative tool.

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