Skip to main content
Glama

getecoback-raumklima

oekodesign_hina_klasse_aus_hauptfunktion

Read-only

Die dokumentierte Hauptfunktion von vorhandenen Router-, Schalter- oder Zugangspunktfunktionen trennen — Read the documentary HiNA class without promoting ordinary Wi-Fi equipment to high availability.

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": {
      "vernetzt_belegt": "<vernetzt_belegt>",
      "hauptfunktion": "<hauptfunktion>",
      "routing_switch_ap": "<routing_switch_ap>",
      "funktionsliste_vollstaendig": "<funktionsliste_vollstaendig>"
    },
    "name": "oekodesign_hina_klasse_aus_hauptfunktion"
  }
}

Input Schema

NameRequiredDescriptionDefault
hauptfunktionYesDokumentierte Hauptfunktion nach Anhang I, keine Ableitung aus einem WLAN-Symbol.
vernetzt_belegtYesNetzwerkfähigkeit und geeigneter Netzwerk-Port des konkreten Geräts aus den Unterlagen belegt?
routing_switch_apYesSind Router-, Netzwerk-Schalter- oder Zugangspunktfunktionen tatsächlich ausgewiesen?
funktionsliste_vollstaendigYesVollständige modellbezogene Überprüfung der Funktionsliste vorhanden?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish that this is a read-only, closed-world operation. Beyond that, the description adds meaningful domain behavior: the classification is documentary rather than inferred from hardware symbols, and ordinary Wi-Fi equipment must not be upgraded to high availability. It does not contradict the annotations.

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 description is compact and front-loads the action before adding the caution about ordinary Wi-Fi equipment. The bilingual phrasing is slightly awkward but does not introduce unnecessary length.

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 tool with four required parameters and no output schema, the description explains the core distinction but does not say what the return value looks like or how the inputs are combined into a result. Combined with annotations and full schema coverage, it is adequate but leaves noticeable gaps about the output.

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 required parameters are already documented in the schema, including both enums. The description mentions the relevant concepts of documented main function and router/switch/access-point functions, but adds no syntax, enum meaning, or decision logic beyond what the schema provides.

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 specific action — reading the documentary HiNA class from documented main-function data — and clarifies that ordinary Wi-Fi equipment must not be promoted to high availability. It is clear what the tool does, but it does not explicitly distinguish itself from any named sibling tool.

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?

The description implies the tool is used when determining a documentary HiNA class from existing router, switch, or access-point information, and warns against treating ordinary Wi-Fi equipment as high availability. However, it gives no explicit when-to-use conditions, prerequisites, or alternative tools for other classification questions.

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