Skip to main content
Glama

getecoback-climate-weather

oskar_luftbefeuchter_zielstufe_dokumentiert

Read-only

Eine gewünschte feste Zielstufe mit der dokumentierten Regelung von Oskar oder Oskar little abgleichen — Check whether Oskar or Oskar little documents the requested target-humidity control setting.

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": {
      "modell": "<modell>",
      "gewuenscht": "<gewuenscht>",
      "automatische_regelung_noetig": "<automatische_regelung_noetig>"
    },
    "name": "oskar_luftbefeuchter_zielstufe_dokumentiert"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesVollständig bestätigtes Modell im Angebot.
gewuenschtYesGewünschte dokumentierte Zielstufe in relativen Prozent; keine Empfehlung.
automatische_regelung_noetigYesIst automatische Zielstufenregelung eine feste Voraussetzung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 safety profile is covered by structured data. The description is consistent with that (a 'check' is a read-only comparison) but adds almost nothing beyond it — no statement of what a negative result means, whether an unknown model is acceptable, or how strictly the documented stage must match.

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?

Short and front-loaded, with the operative clause first. The German/English duplication is redundant filler for a bilingual audience but costs little and does not obscure meaning.

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 description should explain what the 'check' actually yields, since nothing else does. That return-value gap is the main incompleteness; the input side is adequately covered by the schema.

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%, including an enum for 'modell' and 0-100 bounds on 'gewuenscht', so the schema carries the parameter burden and the baseline of 3 applies. The description restates the gist of 'gewuenscht' ('requested target-humidity control setting') but adds no clarification of what the 'automatische_regelung_noetig' flag changes about the comparison.

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 definition names a specific resource (Oskar / Oskar little documented target-stage control) and a verb of sorts ('abgleichen' / 'Check whether ... documents'), so the agent knows this is a verification rather than a configuration tool. However, 'abgleichen' is vague about the actual operation — it never states whether it returns a match verdict, the documented stage, or a compatibility assessment, and it does nothing to distinguish itself from the many other luftbefeuchter_* / befeuchter_* siblings.

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?

No when-to-use guidance, no prerequisites, and no mention of alternative tools for related questions (e.g. the model-care or replacement-routine siblings). The agent must infer the call context 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