Skip to main content
Glama

getecoback-climate-weather

ventilator_fernbedienung_nutzplaetze

Read-only

Eine Fernbedienung am eigenen Bett und Sitzplatz anhand wiederholter Versuche vergleichen — Compare observed remote-control reception at two usual fan-use positions.

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": {
      "versuche_je_ort": "<versuche_je_ort>",
      "erfolge_a": "<erfolge_a>",
      "erfolge_b": "<erfolge_b>",
      "gleicher_befehl": "<gleicher_befehl>"
    },
    "name": "ventilator_fernbedienung_nutzplaetze"
  }
}

Input Schema

NameRequiredDescriptionDefault
erfolge_aYesErfolgreiche gleiche Befehle von Position A aus.
erfolge_bYesErfolgreiche gleiche Befehle von Position B aus.
gleicher_befehlYesBefehl, Batteriezustand und Gerätestellung waren jeweils gleich?
versuche_je_ortYesVersuche je Ort unter vergleichbaren Bedingungen, mindestens 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 and the description's burden is lower. It adds the meaningful constraint that trials must be comparable, but with no output schema it does not say what the comparison returns (a rate difference, a verdict, a recommendation), which is the main behavioral gap.

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?

Two tight sentences with the purpose front-loaded and the method trailing; the bilingual German/English pairing is near-duplicative but serves clarity for mixed-language agents. No filler or hedging.

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?

A four-required-parameter computational tool with full schema coverage and no output schema: the inputs are adequately specified, but the description never characterises the result the agent will receive, which matters when there is no output schema to fall back on.

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 all four parameters (erfolge_a, erfolge_b, gleicher_befehl, versuche_je_ort) are already documented with ranges and meaning. The description adds no semantics beyond what the schema states, which is the expected baseline-3 case when the schema does the heavy lifting.

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?

Names a specific verb (vergleichen/compare) and a specific resource (remote-control reception at the bed vs. seat positions) with the method (repeated trials) stated up front. An agent can tell this is a two-position comparison experiment, not a measurement or a setup tool; it is only slightly weaker than a 5 because it never explicitly contrasts itself with the other ventilator_* siblings.

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 phrase 'anhand wiederholter Versuche' combined with the required 'gleicher_befehl' flag implies the usage precondition (controlled, repeated, comparable trials), but the description never states when to choose this over another ventilator tool or when the comparison is invalid. Usage is inferred rather than instructed.

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