Skip to main content
Glama

getecoback-raumklima

elektrog_altgeraete_flaechenbasis_haendler

Read-only

Beim stationären oder entfernten Verkauf prüfen, ob der belegte Flächenwert zur richtigen Bezugsgröße der allgemeinen Händlerregel gehört — Match a verified area to the proper shop or distance-selling threshold.

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": {
      "kanal": "<kanal>",
      "bereich": "<bereich>",
      "flaechenart": "<flaechenart>",
      "flaeche_m2": "<flaeche_m2>",
      "elektroangebot": "<elektroangebot>"
    },
    "name": "elektrog_altgeraete_flaechenbasis_haendler"
  }
}

Input Schema

NameRequiredDescriptionDefault
kanalYesKanal des tatsächlich zuständigen Anbieters.
bereichYesFür wen wurde die Flächenzahl erhoben?
flaeche_m2YesBelegte Quadratmeter anhand derselben Bezugsgröße, sonst 0 bei offener Flächenart.
flaechenartYesExakte dokumentierte Bezugsgröße.
elektroangebotYesZeitbezug des Elektronikangebots eines Lebensmittelvertriebs.

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 establish that this is a safe read-only, closed-world check. Beyond that the description only says a value is 'matched' against a threshold; it does not say what a mismatch vs. match produces or whether 'offen' inputs change the verdict, which matters for a decision tool.

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 tight clauses, front-loaded with the usage condition and the check itself. The German/English duplication is mildly redundant but keeps it skimmable; no filler sentences.

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 five-parameter rule-check tool with no output schema, the definition explains the purpose but not the result shape or how a failed match should be interpreted. An agent can call it but cannot predict what the response represents.

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% with four enums, so each parameter is already well documented. The description adds the framing that the area must belong to the 'richtige Bezugsgröße' but no parameter-level meaning beyond the schema.

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') and a concrete resource ('belegter Flächenwert' vs. 'Bezugsgröße der allgemeinen Händlerregel'), and scopes it to stationary versus distance selling. It is clear what the tool does, though it does not name or contrast any sibling rule-check 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?

It states the business context in which to use it ('Beim stationären oder entfernten Verkauf'), which is useful implied guidance. It gives no when-not-to-use condition and points to no alternative tool for adjacent checks.

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