Skip to main content
Glama

getecoback-climate-weather

brause_fliessdruck_bereich

Read-only

Gemessenen Fließdruck mit dem dokumentierten Brausenbereich abgleichen — Check a measured running pressure against the specified showerhead range.

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": {
      "druck_bar": "<druck_bar>",
      "betriebsdruck": "<betriebsdruck>",
      "untergrenze_bar": "<untergrenze_bar>",
      "obergrenze_bar": "<obergrenze_bar>"
    },
    "name": "brause_fliessdruck_bereich"
  }
}

Input Schema

NameRequiredDescriptionDefault
druck_barYesAbgelesener Druck in bar.
betriebsdruckYesWurde der Druck bei laufender Entnahme am vorgesehenen Messpunkt erfasst?
obergrenze_barYesDokumentierter maximaler Fließdruck in bar.
untergrenze_barYesDokumentierter minimaler Fließdruck in bar.

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 that this is a comparison rather than a capture, but says nothing about boundary handling (inclusive vs. exclusive limits), tolerance, or what verdict the caller receives — meaningful gaps for a pure check tool with no output schema.

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, front-loaded with the verb, and the bilingual pairing is compact. The English sentence is a near-verbatim translation rather than added information, so it fills space without adding content.

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?

For a four-required-parameter read-only check with no output schema, an agent still lacks the crucial detail of what the call returns (pass/fail, delta, range echo) and how the optional bool is interpreted. The description covers the input side adequately but leaves the result side undefined.

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 the schema already defines all four parameters with units (bar) and bounds. The description only restates that one value is measured and two form the documented range; it adds no semantics about how betriebsdruck (measurement taken during draw-off) affects the comparison, which would have been genuinely useful.

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 specific verb (abgleichen / "Check ... against") and a specific resource (measured Fließdruck vs. documented showerhead range), so an agent can tell this is a range-compliance check rather than a measurement tool. It does not name any sibling, so the distinction from tools like duschdurchfluss_messen rests on the phrasing alone.

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 implicitly conveyed: the tool applies where a measured pressure exists and a documented min/max range is known. There is no explicit statement of when to prefer it over a measuring tool, no preconditions (e.g. pressure must have been taken at the designated measuring point), and no 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