Skip to main content
Glama

getecoback-climate-weather

pc_ansaugluft_drei_ablesungen_eigenes_stillstandsband

Read-only

Aus drei gleichartigen Ansaugluftablesungen die beobachtete Schwankung prüfen, bevor eine kurze Phase als stationär beschrieben wird — Verify a recorded inlet plateau across three unchanged operating samples.

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": {
      "anfang_c": "<anfang_c>",
      "mitte_c": "<mitte_c>",
      "ende_c": "<ende_c>",
      "band_k": "<band_k>",
      "gleiche_laufart": "<gleiche_laufart>"
    },
    "name": "pc_ansaugluft_drei_ablesungen_eigenes_stillstandsband"
  }
}

Input Schema

NameRequiredDescriptionDefault
band_kYesSelbst begründete maximale Schwankung innerhalb der drei Ablesungen.
ende_cYesDritter Wert am Ende des Abschnitts.
mitte_cYesZweiter Ansaugluftwert im Abschnitt.
anfang_cYesAnsaugluftwert zu Beginn des gleichartigen beobachteten Abschnitts.
gleiche_laufartYesAufgabe, Messort und relevanter Gerätezustand sind unverändert belegt.

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 and the bar is lower. The description adds the comparison logic behind band_k (observed variation against a self-justified maximum), but says nothing about what the result looks like or what happens when the variation exceeds the band, and there is no output schema to compensate.

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?

One compact sentence, front-loaded with the measurement task before the verification clause. The German/English duplication costs some space but is justified by the mixed-language tool name and schema.

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?

With five required parameters and no output schema, the definition covers the purpose and the comparison logic but omits what the tool returns (a pass/fail verdict, a plateau declaration, or a diagnostic message). For a read-only, side-effect-free check this is an acceptable but noticeable gap.

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 every parameter already carries a constraint and explanation, so the schema does the heavy lifting. The description does not add format, ordering, or edge-case guidance beyond it, which is the expected baseline of 3.

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 verb (prüfen/verify) and resource (drei gleichartige Ansaugluftablesungen / recorded inlet plateau), and adds the decision context 'before a short phase is described as stationary'. It is clearly distinguishable from sibling sampling tools by its three-sample variation check, though it does not name a sibling explicitly.

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 rather than stated: the check is a precondition for declaring a phase stationary. There is no explicit statement of when not to use it, nor an alternative tool for a single reading or a longer window, so an agent must infer the boundary.

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