Skip to main content
Glama

getecoback-climate-weather

terrasse_bodenluft_schattenprobe_getrennte_messwerte

Read-only

Bei einer eigenen Beschattungsprobe Änderungen am Belag und in der Luft getrennt darstellen — Separate surface temperature and air observations from a paired shade 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": {
      "belag_unbeschattet_c": "<belag_unbeschattet_c>",
      "belag_beschattet_c": "<belag_beschattet_c>",
      "luft_unbeschattet_c": "<luft_unbeschattet_c>",
      "luft_beschattet_c": "<luft_beschattet_c>",
      "messbedingungen_vergleichbar": "<messbedingungen_vergleichbar>"
    },
    "name": "terrasse_bodenluft_schattenprobe_getrennte_messwerte"
  }
}

Input Schema

NameRequiredDescriptionDefault
luft_beschattet_cYesLuftwert mit betrachteter Maßnahme an derselben Stelle.
belag_beschattet_cYesGemessene Belagtemperatur mit Schatten.
luft_unbeschattet_cYesGemessener Luftwert an derselben belüfteten, vor direkter Sonne geschützten Stelle ohne Maßnahme.
belag_unbeschattet_cYesGemessene Belagtemperatur ohne betrachteten Schatten.
messbedingungen_vergleichbarYesMessverfahren, Tageszeit und übrige Bedingungen vergleichbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 safety is covered and the bar is lower. The description adds the key behavioral point that the two measurement tracks are reported separately, but it never states what happens when messbedingungen_vergleichbar is false (rejection, warning, or silent pass) nor what the returned separation looks like — a real gap for a computation-style tool.

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 short, front-loaded clauses with no filler. The German and English sentences are semantic duplicates, which is defensible for a bilingual catalog but adds no information for the agent.

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 five required numeric parameters forming a paired comparison, a comparability gate, and no output schema, the description should say what the tool returns (e.g. the two deltas) and how the comparability flag affects the result. Neither is present, so an agent cannot predict the response shape or the failure mode.

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% and each of the five parameters carries a German description with bounds, so the schema does the heavy lifting. The description's only added meaning is the pairing of 'Belag' and 'Luft' values, which the parameter names already convey; no units, comparability thresholds, or plausibility rules are supplied 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 operation (separating the surface-temperature and air components of a paired shade trial) and the resource it operates on, so an agent knows this is a derived-measurement tool rather than a raw capture tool. It does not, however, distinguish itself from the many sibling 'terrasse_*' shade/measurement tools by name or scope.

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?

'Bei einer eigenen Beschattungsprobe' implies the triggering context: the agent should use this when it holds its own paired shaded/unshaded readings. There is no explicit when-not guidance, no mention of what to do when the trial is not comparable, and no named alternative for raw or single-site logging.

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