Skip to main content
Glama

getecoback-climate-weather

pc_zwei_ansaugseiten_lokal_mehrlast_probe

Read-only

Nach unabhängiger Zuordnung der vorhandenen Ansaugbereiche entscheiden, ob ein einzelner äußerer Messpunkt beide abbildet — Test whether one inlet observation can stand for two documented intake locations.

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": {
      "gehaeuseseite_a_c": "<gehaeuseseite_a_c>",
      "gehaeuseseite_b_c": "<gehaeuseseite_b_c>",
      "messgrenze_c": "<messgrenze_c>",
      "beide_ansaug_und_nicht_versperrt": "<beide_ansaug_und_nicht_versperrt>"
    },
    "name": "pc_zwei_ansaugseiten_lokal_mehrlast_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
messgrenze_cYesEigene Toleranz für diese Frage in K.
gehaeuseseite_a_cYesZeitgleiche Lufttemperatur außen an Ansaugbereich A.
gehaeuseseite_b_cYesZeitgleiche Lufttemperatur außen an unabhängig bestätigtem Ansaugbereich B.
beide_ansaug_und_nicht_versperrtYesBeide Positionen sind am vorhandenen Aufbau eindeutig Ansaugpunkte und wurden frei beobachtet.

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?

readOnlyHint=true and openWorldHint=false already tell the agent this is a side-effect-free, closed-world computation, so the annotation bar is lower. The description adds the sequencing precondition (independent assignment first), which is real information the annotations do not carry. It does not, however, say what the tool returns — a verdict, a boolean, a tolerance verdict plus marginal — which matters because there is no output schema to fall back on.

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?

A single sentence, front-loaded with the precondition and then the decision, with a bilingual dash gloss rather than a repeated paragraph. Nothing is wasted; the only cost is that the doubled German/English phrasing makes it slightly slower to parse than a single-language statement.

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?

Four required parameters, no optional ones, no output schema, and a read-only annotation — the description covers the setup condition, so it is serviceable. The notable gap is that the decision rule and the result format are never characterized, which for a probe whose entire value is its verdict leaves the agent guessing at the return.

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% and every parameter carries its own German description (temperature at A, temperature at B, own tolerance in K, both positions confirmed unobstructed), so the schema does the heavy lifting. The description's phrase 'einzelner äußerer Messpunkt beide abbildet' loosely frames the A/B comparison but adds no format, unit, or tolerance-interpretation detail beyond the schema. Baseline 3 applies.

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 states a concrete decision: after independently assigning the existing intake areas, decide whether a single outer measurement point represents both documented intake locations. That is a specific operation ('decide whether one measurement represents two locations'), not a restatement of the encoded name. It does not distinguish itself from adjacent electronics/intake probes such as pc_ansaugluft_drei_ablesungen_eigenes_stillstandsband or pc_ansaugluft_zu_raum_und_auslass, so it falls short of a 5.

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?

A genuine precondition is given — the intake areas must already have been independently assigned before this test is meaningful. However, there is no statement of when NOT to use it, and no named alternative for the case where the assignment is not yet done or where more than two intake points are in play. Usage is implied rather than routed.

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