Skip to main content
Glama

getecoback-raumklima

arbeitsplatz_oberflaeche_sonnenstreifen_messpunkte

Read-only

Die am Schreibtisch erwärmte Fläche von einer zugleich beschatteten Stelle und dem zugehörigen Luftwert getrennt beschreiben — Compare paired desk surfaces and concurrent air without assuming either surface represents the 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": {
      "helle_flaeche_c": "<helle_flaeche_c>",
      "schatten_flaeche_c": "<schatten_flaeche_c>",
      "luft_c": "<luft_c>",
      "material_und_messweise_gleich": "<material_und_messweise_gleich>"
    },
    "name": "arbeitsplatz_oberflaeche_sonnenstreifen_messpunkte"
  }
}

Input Schema

NameRequiredDescriptionDefault
luft_cYesZeitgleicher Luftwert am vorgesehenen Sitzplatz, außerhalb direkter Bestrahlung des Fühlers.
helle_flaeche_cYesMesswert eines markierten beleuchteten Oberflächenpunkts am Arbeitsplatz.
schatten_flaeche_cYesZeitgleicher Messwert einer beschatteten Stelle aus vergleichbarem Material.
material_und_messweise_gleichYesFür die zwei Oberflächenstellen gleiche geeignete Messweise bei vergleichbarem Material belegt.

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. The description adds a genuine methodological stance beyond that — keep the two surfaces and the air value separate and do not let either surface stand in for the room — but says nothing about the shape of the result, how mismatched inputs are handled, or what invariant is enforced. Useful context, but not rich behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core constraint is front-loaded and clear, but the content is given twice — once in German and again in an English sentence that restates it nearly verbatim. That duplication costs space without adding information, though the individual sentences themselves contain no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, four-parameter comparison tool with a fully described schema, the description supplies the one thing the schema cannot: the interpretive rule that neither surface represents the room. Since no output schema exists, a note on what the comparison yields would help, but an agent can call this correctly without further information.

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 (luft_c, helle_flaeche_c, schatten_flaeche_c, material_und_messweise_gleich) are already fully documented with ranges and meaning in the schema. The description reinforces the pairing requirement conceptually but adds no units, tolerances, or interpretation rules beyond the schema. Baseline 3 applies.

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 concrete object (paired desk surface readings: one warmed/lit spot, one shaded spot, plus the concurrent air value) and states that they are to be described separately rather than merged. This distinguishes it from siblings that treat a single point as room-representative. The verb 'beschreiben' stays somewhat abstract about what the tool actually returns or computes, which keeps it short of a 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 implied rather than stated: use it when you have a warmed surface, a simultaneously shaded counterpart, and a concurrent air reading, and you must not generalize either surface to the room. No explicit 'use X instead when…' routing to siblings such as arbeitsplatz_ersatzraum_ruhe_waerme_vergleich or arbeitsplatz_tischluefter_messabdeckung_abseits_strahl is given, and there are no stated exclusions.

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