Skip to main content
Glama

getecoback-climate-weather

entfeuchter_nennwert_und_messvolumen_scope

Read-only

Bei dokumentiert konstantem Prüfpunkt das tatsächlich erfasste Teilvolumen richtig beschriften — Report captured water without equating a partial collection with a nameplate rating.

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": {
      "gesammelt_l": "<gesammelt_l>",
      "laufzeit_h": "<laufzeit_h>",
      "nennweg": "<nennweg>",
      "pruefpunkt_stabil": "<pruefpunkt_stabil>"
    },
    "name": "entfeuchter_nennwert_und_messvolumen_scope"
  }
}

Input Schema

NameRequiredDescriptionDefault
nennwegYesWie wurde Wasser im Protokoll erfasst?
laufzeit_hYesDauer des gesamten Protokollfensters in Stunden einschließlich möglicher Pausen.
gesammelt_lYesWährend der protokollierten Zeit tatsächlich aufgefangenes Wasser in Liter.
pruefpunkt_stabilYesTemperatur und relative Feuchte waren beim Durchlauf stabil und dokumentiert?

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 safety is covered. The description adds the meaningful semantic guard that a partial collection must not be reported as a nameplate rating, which is real behavioral value. It does not say what the tool returns (a label, a corrected figure, or a verdict) or how ambiguous collection methods are resolved.

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 sentences with the condition front-loaded and no filler. The German and English halves largely restate the same point, a minor redundancy that costs some efficiency but not clarity.

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?

All four required parameters are fully described in the schema and the annotations cover the safety profile, so the core is sufficient. However, with no output schema the description should indicate what the call yields (a label versus a computed value), and it is silent on that and on the handling of unclear collection paths.

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 including the enum for collection method are already documented, which sets the baseline at 3. The description gestures at 'pruefpunkt_stabil' and the partial-volume case but adds no format, unit, or edge-case semantics 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?

States a specific action on a specific resource: correctly labelling the actually captured partial volume against a documented constant test point, and explicitly contrasting it with a nameplate rating. The intent (a scope/labelling determination, not a measurement) is inferable, though the abstract framing and mixed German/English wording make it less immediately identifiable than a clean verb+resource statement.

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?

It gives one precondition — the test point must be documented as constant — which implies when the tool applies. It gives no exclusions, no guidance for the 'ungeklaert' case, and does not name or route to any sibling such as the energy-per-litre or test-point tools, leaving the agent to infer boundaries.

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