Skip to main content
Glama

getecoback-climate-weather

heizwaerme_arbeitsplatz

Read-only

Persönliche Wärme oder Raumheizung am Arbeitsplatz nach Bedarf einordnen — Decide how to address local discomfort or an underheated room.

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": {
      "entire_room_cold": "<entire_room_cold>",
      "beside_cold_surface": "<beside_cold_surface>",
      "fixed_work_schedule": "<fixed_work_schedule>"
    },
    "name": "heizwaerme_arbeitsplatz"
  }
}

Input Schema

NameRequiredDescriptionDefault
entire_room_coldYesIst der Raum insgesamt zu kühl?
beside_cold_surfaceYesLiegt der Sitzplatz direkt an einer kalten Scheibe oder im Luftzug?
fixed_work_scheduleYesWird der Raum zu wiederkehrenden Zeiten genutzt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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, covering the safety profile. The description only says it is a decision/assessment and does not disclose what decision categories or output are produced; with no output schema, the behavioral value beyond annotations is thin.

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-loads the purpose. The German-English duplication adds some redundancy, but there is little filler and no confusing structure.

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?

For a read-only decision tool with three required inputs and no output schema, the description does not say what result is returned or how to act on it. It identifies the domain but is not complete enough for an agent to interpret the decision output.

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?

All three required booleans are fully described in the schema at 100% coverage, so the baseline is 3. The description does not add meaning about how entire_room_cold, beside_cold_surface, and fixed_work_schedule combine into a recommendation.

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?

States a specific decision-support action ('einordnen'/'Decide how to address') and resource ('Persönliche Wärme oder Raumheizung am Arbeitsplatz' / local discomfort or underheated room). It distinguishes local discomfort from an underheated room, but does not name or differentiate itself from nearby heating-assessment 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 description implies when to use it: for local discomfort or an underheated room at a workplace. It does not state when not to use it or name alternatives such as heater checks, BTU recommendations, or device selection tools.

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