Skip to main content
Glama

getecoback-climate-weather

lueftung_betriebspunkt_datenform_zwischenwert

Read-only

Prüft ob der angefragte Druckpunkt exakt dokumentiert oder nur zwischen benachbarten Zeilen liegt — Determine whether a requested pressure point has a direct documented match.

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": {
      "anfrage_pa": "<anfrage_pa>",
      "untere_pa": "<untere_pa>",
      "obere_pa": "<obere_pa>",
      "gleicher_luftstrom": "<gleicher_luftstrom>"
    },
    "name": "lueftung_betriebspunkt_datenform_zwischenwert"
  }
}

Input Schema

NameRequiredDescriptionDefault
obere_paYesHöherer dokumentierter Druckpunkt in Pa.
untere_paYesNiedrigerer dokumentierter Druckpunkt in Pa.
anfrage_paYesExterner Druck in der Anfrage in Pa.
gleicher_luftstromYesBeide Werte gelten beim gewünschten Volumenstrom und in derselben Variante.

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 usefully adds that the check distinguishes an exact documented match from an interpolation between adjacent rows, but it does not state what the tool actually returns (boolean, enum, or structured result), which is the main behavioral gap for a read-only check.

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 clauses, front-loaded with the check itself and followed by the two possible outcomes. The bilingual duplication is slightly redundant but not confusing, and there is no filler.

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 simple four-parameter, read-only check with full schema coverage, the description covers what is being tested and the two outcomes. Because there is no output schema, it should still say what the return value looks like, which it omits.

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 are already documented in the schema. The description's phrasing clarifies the relationship between the requested point and the lower/upper documented bounds, but adds no format, ordering, or validation details 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 uses a specific verb ('Prüft' / 'Determine') on a specific resource (a requested pressure point versus documented rows) and names both possible outcomes: exact documentation or lying between adjacent rows. It does not explicitly differentiate itself from any sibling, but the operation is unambiguous on its own.

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 by the purpose: call this to classify a requested pressure point against documented data. There is no explicit statement of when to use it versus alternatives, no prerequisites, and no exclusions, so an agent must infer the context.

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