Skip to main content
Glama

getecoback-climate-weather

kuechenarbeitsplatte_zwei_freizonen_einmal_abziehen

Read-only

Auf der Arbeitsplatte zwei überlappende, bereits freigehaltene Bereiche bei der nutzbaren Fläche nur einmal abziehen — Reconcile overlapping retained clear areas on a countertop.

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": {
      "flaeche_cm2": "<flaeche_cm2>",
      "zone_a_cm2": "<zone_a_cm2>",
      "zone_b_cm2": "<zone_b_cm2>",
      "gemeinsame_cm2": "<gemeinsame_cm2>",
      "belegung_cm2": "<belegung_cm2>"
    },
    "name": "kuechenarbeitsplatte_zwei_freizonen_einmal_abziehen"
  }
}

Input Schema

NameRequiredDescriptionDefault
zone_a_cm2YesDavon erste gemessene unbenutzbare oder freigehaltene Fläche.
zone_b_cm2YesDavon zweite gemessene unbenutzbare oder freigehaltene Fläche.
flaeche_cm2YesTatsächlich vermessene ebene Arbeitsfläche in cm².
belegung_cm2YesPlatz der vorgesehenen Gegenstände laut bereits geprüftem Aufstellplan.
gemeinsame_cm2YesBereich, der in beiden Zonen enthalten ist.

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 declare readOnlyHint=true and openWorldHint=false, so the safe-read profile is covered. The description adds the key behavioral nuance that overlap must not be double-counted, which is genuine value, but it says nothing about the returned value, and it silently omits any role for belegung_cm2.

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?

A single front-loaded sentence captures the core rule, with a bilingual restatement that costs a few words but aids disambiguation. Dense but free of filler; nothing structurally wasteful beyond the mirrored English clause.

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?

Five required numeric parameters, no output schema, and a non-trivial arithmetic contract make the description's burden high. It explains the overlap rule but leaves open whether the planned-footprint area is also deducted and what the result represents, which an agent needs before calling.

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 every parameter already carries a German description and baseline is 3. The description adds meaning specifically for gemeinsame_cm2 by stressing single-counting of the overlap, but gives no hint about how belegung_cm2 (planned object footprint) participates in the calculation.

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 operation (subtracting two overlapping retained clear areas from the usable area only once) on a specific resource (countertop). An agent can infer this is an inclusion-exclusion area computation rather than a generic update or lookup, though it never states what the tool actually returns.

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 is only implied by the domain vocabulary: measured free zones on a worktop that overlap. There is no explicit when-to-use statement, no exclusion, and no mention of how this differs from the many sibling tools, so the agent must infer applicability from the scenario alone.

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