Skip to main content
Glama

getecoback-climate-weather

arbeitsplatz_tischluefter_messabdeckung_abseits_strahl

Read-only

Bei einem örtlichen Lüfterversuch Raumrepräsentanz nur mit zeitgleichen Ablesungen außerhalb des direkten Luftstroms beurteilen — Separate in-stream and off-stream data completeness in a desk fan trial.

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": {
      "luefterpaare": "<luefterpaare>",
      "beides_erfasst": "<beides_erfasst>",
      "nur_strahl": "<nur_strahl>",
      "referenzposition_bestaetigt": "<referenzposition_bestaetigt>"
    },
    "name": "arbeitsplatz_tischluefter_messabdeckung_abseits_strahl"
  }
}

Input Schema

NameRequiredDescriptionDefault
nur_strahlYesWeitere Paare mit nur am Luftstrompunkt abgelesenem Wert.
luefterpaareYesZeitgleich geplante Paare aus Strahlmesspunkt und abseits liegendem Referenzpunkt.
beides_erfasstYesDavon Paare mit beiden belegten Messpunkten.
referenzposition_bestaetigtYesDer Referenzpunkt blieb außerhalb des direkten Stroms, bei gleicher Messweise.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 and locality profile is settled. The description adds the analytical framing that in-stream and off-stream completeness are handled separately, which is genuine context beyond the annotations. It says nothing about the result, error conditions (e.g. inconsistent counts), or how the boolean reference confirmation changes the outcome, so it does not fill the remaining 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.

Conciseness3/5

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

It is short — a single German sentence followed by an English gloss after the em dash — with no padding sentences. But the German clause is densely nominalized and hard to parse, and the bilingual restatement is largely duplicative rather than complementary. Brevity is achieved at the cost of readability.

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?

With four required numeric/boolean parameters and no output schema, the description must carry the burden of explaining what the agent gets back and how the counts are interpreted — it does not. It also omits what happens when 'beides_erfasst' and 'nur_strahl' are inconsistent or exceed 'luefterpaare'. For a computation-style tool with zero return documentation, this is a material gap.

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%: all four parameters carry their own descriptions, bounds and the boolean's semantics, so the schema does the heavy lifting. The description's in-stream/off-stream split loosely maps onto nur_strahl versus beides_erfasst/luefterpaare, giving mild conceptual orientation, but it adds no arithmetic or consistency rules beyond that. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the scenario (a desk fan trial at a local workplace) and the analytical objective ('Raumrepräsentanz ... beurteilen', separating in-stream and off-stream data completeness), so the domain is identifiable. However, it never states what the tool actually produces — a completeness verdict, a ratio, a validation pass — leaving the verb function ambiguous relative to the four count-based parameters. An agent reading only this would know the topic but not the operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only conditioning signal is an implicit methodological rule: representativeness should be judged only with simultaneous readings outside the direct airflow ('nur mit zeitgleichen Ablesungen außerhalb des direkten Luftstroms'). There is no statement of when to call this versus any sibling, no prerequisites, and no exclusions. The sibling list contains several fan/measurement tools, yet none is referenced or ruled out.

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