Skip to main content
Glama

getecoback-climate-weather

h2861bp_plus_hfc_tabellenspalte_und_ebenenbezug

Read-only

Beim H 2861 BP die passende Tabellenkennzeichnung und zwei unterschiedlich bezeichnete Ebenen einordnen — Check +HFC versus −HFC and keep rail and food positions distinct.

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": {
      "exakte_de_variante": "<exakte_de_variante>",
      "tabelle": "<tabelle>",
      "hfc70_c_im_abgleich": "<hfc70_c_im_abgleich>",
      "schienenebene": "<schienenebene>",
      "gargutebene": "<gargutebene>",
      "beide_ebenen_eindeutig": "<beide_ebenen_eindeutig>"
    },
    "name": "h2861bp_plus_hfc_tabellenspalte_und_ebenenbezug"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabelleYesIn der ausgewählten Handbuchspalte tatsächlich gelesene Kennzeichnung.
gargutebeneYesIn der Tabelle oder Beobachtung ausdrücklich getrennt angegebene Gargutebene.
schienenebeneYesUnabhängig belegte physische Schienenebene, Platzhalter 1 bei ungeklärtem Bezug.
exakte_de_varianteYesBestätigter H 2861 BP Edelstahl/CleanSteel, Materialnummer 12144610, mit passender deutscher Anleitung.
hfc70_c_im_abgleichYesIst in der dokumentierten betrachteten Konfiguration HFC 70-C vorhanden?
beide_ebenen_eindeutigYesSind die beiden eingetragenen Ebenen ausdrücklich verschieden bezeichnet und beide Angaben belegt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/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 the safety profile is covered. Beyond that the description adds little: it does not say what a positive or negative HFC match produces, whether conflicting levels cause an error, or what the caller receives, and with no output schema that gap matters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the H 2861 BP context, but the abrupt German/English mix and the em-dash fragment make it read as a scribbled note rather than a structured definition. No sentence is wasted, yet the second clause is elliptical enough to cost clarity.

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?

For a tool with six required parameters, no output schema, and a validation-flavored purpose, the description should explain what a successful versus conflicting submission means. It leaves the agent guessing about the result and about how the 'beide_ebenen_eindeutig' constraint is enforced.

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%, so all six parameters are already documented in the schema, and the baseline is 3. The description reinforces the two key distinctions (HFC present/absent and rail versus food level needing to stay separate), which lightly clarifies intent for 'hfc70_c_im_abgleich', 'schienenebene' and 'gargutebene', but adds no format or edge-case detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the subject (H 2861 BP), the objects being aligned ('Tabellenkennzeichnung', two differently labeled levels), and the discriminating concepts (+HFC versus −HFC, rail versus food position). However the operative verb 'einordnen' is vague and the tool's actual effect is never stated, so an agent cannot tell whether it validates, records, or returns a comparison result.

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 indication of when this tool should be chosen over any of the many sibling H 2861 BP / appliance-related tools, no preconditions, and no exclusions. The '+HFC versus −HFC' phrasing hints at a comparison scenario but does not phrase it as usage guidance.

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