Skip to main content
Glama

getecoback-raumklima

datenvergleich_punktschaetzung_aufgerundete_klasse

Read-only

Bestimme, wie viele Planungspunkte eines Datensatzes oberhalb einer belegten Gerätegrenze liegen — Count which published planning cases exceed a documented equipment limit

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": {
      "fall_a": "<fall_a>",
      "fall_b": "<fall_b>",
      "fall_c": "<fall_c>",
      "leistung_grenze": "<leistung_grenze>",
      "grundlagen_abgeglichen": "<grundlagen_abgeglichen>"
    },
    "name": "datenvergleich_punktschaetzung_aufgerundete_klasse"
  }
}

Input Schema

NameRequiredDescriptionDefault
fall_aYesPlanungswert für Fall A in gemeinsamer Einheit
fall_bYesPlanungswert für Fall B in derselben Einheit
fall_cYesPlanungswert für Fall C in derselben Einheit
leistung_grenzeYesBelegte Leistung des genauen Gerätebetriebs in derselben Einheit
grundlagen_abgeglichenYesEinheit und Betriebsart sind abgeglichen. Die Planungspunkte sind keine beobachteten Messwerte.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/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, but the description adds little beyond them. It does not say what the result looks like (presumably a count between 0 and 3), how a value exactly equal to the limit is treated ('oberhalb' vs. 'at'), or whether any rounding to a class occurs despite the tool name.

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?

The definition is short and front-loads the core action. The bilingual duplication is mildly redundant but useful for a German-named tool and does not obscure the intent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 description should state what is returned (a count, a class, a boolean per case). It instead leaves the return value and the boundary/tie behavior unspecified, so an agent cannot confidently interpret the result of this comparison.

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 five parameters (fall_a/fall_b/fall_c, leistung_grenze, grundlagen_abgeglichen) are documented in the schema itself. The description only restates that planning values are compared against a limit and adds no syntax or interpretation beyond that, which matches the 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 gives a concrete verb and resource: count how many planning points of a dataset lie above a documented device limit, which is more specific than the opaque tool name. It is weakened by the mismatched 'aufgerundete_klasse' (rounded-up class) in the name, which the description never explains, and by the ambiguous English phrasing 'Count which ... exceed' instead of 'count how many'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool, when not to, or which sibling to prefer for related comparisons; the many sibling tools include similar comparison/estimate operations and nothing routes between them. The only precondition-like signal comes from the schema field 'grundlagen_abgeglichen', not from the description.

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