Skip to main content
Glama

getecoback-raumklima

arbeitsplatz_ersatzraum_ruhe_waerme_vergleich

Read-only

Zwei gemessene Arbeitsplätze für ein Gespräch nach Wärme, erlebter Ruhe und Verfügbarkeit prüfen — Choose between two trial work spots for a specific call.

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": {
      "ziel_min_c": "<ziel_min_c>",
      "a_c": "<a_c>",
      "b_c": "<b_c>",
      "a_ruhig": "<a_ruhig>",
      "b_ruhig": "<b_ruhig>",
      "a_frei": "<a_frei>",
      "b_frei": "<b_frei>"
    },
    "name": "arbeitsplatz_ersatzraum_ruhe_waerme_vergleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_cYesGemessene Temperatur A.
b_cYesGemessene Temperatur B.
a_freiYesIst A im geplanten Termin nutzbar?
b_freiYesIst B im geplanten Termin nutzbar?
a_ruhigYesWar das erprobte Geräuschniveau für das Gespräch in A brauchbar?
b_ruhigYesGeräuschniveau in B brauchbar?
ziel_min_cYesSelbst gewählte Mindesttemperatur für die Gesprächszeit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 safety is covered. What the description omits is the decision behavior: with seven inputs, it never says whether the tool returns a winner, a ranking, or per-criterion verdicts, nor how the temperature values are weighed against ziel_min_c. For a comparison tool with no output schema, that is the central behavior an agent needs.

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 compact sentences, front-loaded with the object of comparison and the criteria. The German/English duplication is slightly redundant and the English rendering drops the three criteria, but nothing is padded.

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?

Seven required parameters with no output schema and no mention of what the comparison yields leaves the agent guessing at the result format and the aggregation rule. The schema documents inputs well, but the description does not compensate for the missing output contract on a multi-criteria decision 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%, so every parameter is already documented, and the description only restates the three criteria dimensions (Wärme, Ruhe, Verfügbarkeit) that map to the a_/b_ pairs. It adds no tie-breaking or threshold semantics beyond the schema. Baseline 3 applies when the schema carries the burden.

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 gives a concrete verb and resource: comparing two measured work spots for a specific call along three named criteria (warmth, experienced quiet, availability). It is clearly distinguishable from generic household-energy siblings. It stops short of naming any sibling alternative, so it lands at 4 rather than 5.

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: the agent must infer that this is a pre-call decision aid between two candidate spots. There is no explicit when-to-use, no when-not-to-use, and no pointer to alternatives such as the room-change or heat-pause siblings. Adequate context, but no guidance.

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