Skip to main content
Glama

getecoback-raumklima

arbeitsplatz_warme_optionen_unterschiedlicher_zielbereich

Read-only

Persönlichen Wärmekomfort und gemessenen Raumwunsch bei zwei vorhandenen Routinen separat abgleichen — Compare observed personal comfort and room warming as different completion criteria.

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": {
      "a_komfort_bestaetigt": "<a_komfort_bestaetigt>",
      "b_komfort_bestaetigt": "<b_komfort_bestaetigt>",
      "a_raumziel_bestaetigt": "<a_raumziel_bestaetigt>",
      "b_raumziel_bestaetigt": "<b_raumziel_bestaetigt>",
      "beobachtung_vergleichbar": "<beobachtung_vergleichbar>"
    },
    "name": "arbeitsplatz_warme_optionen_unterschiedlicher_zielbereich"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_komfort_bestaetigtYesPersönlicher Wärmewunsch bei Aufgabe mit Ablauf A bestätigt.
b_komfort_bestaetigtYesEntsprechender persönlicher Wunsch bei Ablauf B bestätigt.
a_raumziel_bestaetigtYesSelbst gesetztes Raumziel am vorgesehenen Messpunkt mit A bestätigt.
b_raumziel_bestaetigtYesEntsprechendes tatsächlich gemessenes Raumziel bei B bestätigt.
beobachtung_vergleichbarYesAufgabe und die für beide Fragen jeweils gleichen Bedingungen sind genügend dokumentiert.

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is clear. The description adds that the tool compares personal comfort and room warming as distinct completion criteria, but it does not explain what the comparison produces, how booleans are evaluated, or what happens if observations are not comparable.

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 description is short and front-loaded with the core comparison purpose. The German sentence is followed by an English rendering that largely repeats it, which is mildly redundant, but the overall structure is efficient and there is no unnecessary filler.

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?

The schema fully documents the five boolean inputs, and annotations cover the read-only, closed-world nature. However, with no output schema, the description does not explain what result the comparison returns or how to interpret a successful versus failed comparison, leaving a meaningful gap for an agent invoking the 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 coverage is 100%, so each of the five boolean parameters is already documented in the input schema. The description adds the conceptual framing that comfort and room target are separate completion criteria and that both routines are compared separately, but it does not elaborate on the individual parameters 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 action (separat abgleichen / compare) and a specific resource (personal warmth comfort and measured room target across two existing routines). It also distinguishes the two completion criteria, so an agent can understand what is being compared, though it does not explicitly differentiate itself from the many sibling arbeitsplatz comparison tools.

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?

Usage is only implied by the phrase 'bei zwei vorhandenen Routinen' and 'different completion criteria'; the description does not state when to choose this tool over alternatives or when not to use it. An agent can infer it is for comparing two routines, but no explicit routing guidance is provided.

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