Skip to main content
Glama

getecoback-climate-weather

elektrog_eins_zu_eins_geraeteart_kernfunktionen

Read-only

Für den Austausch eines Haushaltsgeräts gleiche Geräteart und im Wesentlichen gleiche Funktionen getrennt anhand des Belegs einordnen — Check like-for-like scope without inferring functional equivalence from a common marketing category.

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": {
      "neue_abgabe": "<neue_abgabe>",
      "gleiche_art": "<gleiche_art>",
      "kernfunktionen": "<kernfunktionen>",
      "genaue_geraete_belegt": "<genaue_geraete_belegt>"
    },
    "name": "elektrog_eins_zu_eins_geraeteart_kernfunktionen"
  }
}

Input Schema

NameRequiredDescriptionDefault
gleiche_artYesGehören Alt- und Neugerät nach den überprüften Gerätebeschreibungen zur gleichen Geräteart?
neue_abgabeYesStatus der tatsächlich dokumentierten Abgabe eines Neugeräts an den Endnutzer.
kernfunktionenYesErfüllen Alt- und Neugerät im Wesentlichen dieselben bestätigten Funktionen?
genaue_geraete_belegtYesBeide Beschreibungen gelten für die konkret betroffenen Geräte?

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?

Annotations already establish that this is a safe, closed-world read (readOnlyHint=true, openWorldHint=false), so the description does not need to restate that. It adds real behavioral content instead: the classification must be made 'anhand des Belegs' and must not be derived from a shared marketing category, which constrains how the judgement is reached — something no structured field conveys.

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?

Two sentences, front-loaded with the operative instruction before the caveat, with no filler. The English second sentence is a paraphrase rather than a pure translation, which is slightly redundant but does sharpen the constraint for a bilingual reader.

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?

The tool is a small four-input classification with fully documented schema and annotations, and the description covers purpose plus the key inference caveat. It does not indicate what the call returns (no output schema exists) or how unresolved 'offen' outcomes are meant to be handled, which an agent would want before relying on the result.

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 three of four parameters are enums with explicit value semantics, so the schema already carries the burden. The description adds only the general framing that the two dimensions are assessed 'getrennt', which loosely maps to the gleiche_art and kernfunktionen parameters but gives no additional meaning for the enum values or the boolean.

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 action ('gleiche Geräteart und im Wesentlichen gleiche Funktionen getrennt anhand des Belegs einordnen') and the scenario ('für den Austausch eines Haushaltsgeräts'), so the agent knows this is a like-for-like scope assessment grounded in a document. It does not name any sibling tool, so differentiation rests on the phrasing alone.

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 context is implied by 'Für den Austausch eines Haushaltsgeräts', and there is one genuine exclusion ('without inferring functional equivalence from a common marketing category'). However, no alternative tool is named and there is no explicit when-not guidance, leaving the agent to infer boundaries from the sibling list.

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