Skip to main content
Glama

getecoback-raumklima

luftbefeuchter_technik_fotobeleg

Read-only

Klären, ob ein Foto oder die genaue Anleitung die Befeuchtertechnik belegt — Check whether the humidifier operating principle is actually documented.

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": {
      "bildsignal": "<bildsignal>",
      "anleitung": "<anleitung>",
      "modell_geprueft": "<modell_geprueft>"
    },
    "name": "luftbefeuchter_technik_fotobeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
anleitungYesIn der Anleitung bestätigte Technik.
bildsignalYesWas ist im Produktbild erkennbar?
modell_geprueftYesGehört die Anleitung zur vollständigen Variante auf dem Typenschild?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/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 externally. The description adds nothing beyond the purpose restatement: it does not say how the inputs are weighed when photo and manual disagree, what criterion counts as 'documented', or what the caller receives.

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?

It is short and front-loaded, which is good, but the German and English halves largely repeat each other rather than adding complementary detail, so the second half does not fully earn its place.

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?

With three fully documented required parameters and no output schema, the structured fields carry most of the load. However, for a tool whose entire value is a judgment call, the description gives no decision logic or result shape, leaving a real gap for a read-only assessment tool.

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% with clear enum values for bildsignal and anleitung, so the baseline is 3. The description reinforces the photo and manual parameters but says nothing about modell_geprueft (the nameplate-variant match), leaving one of three required inputs without extra framing.

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 decision task: determine whether a photo or the exact instruction manual substantiates the humidifier's operating principle. That is specific enough to distinguish it from the surrounding care/placement maintenance siblings. It stops short of naming any alternative tool or stating what the determination itself looks like.

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 when-to-use or when-not-to-use guidance, no prerequisites, and no named alternative among the many luftbefeuchter_* siblings. The agent must infer the trigger condition from the phrasing 'Klären, ob ...' 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