Skip to main content
Glama

getecoback-climate-weather

maehroboter_uebernommener_garten_aenderungsflaechen

Read-only

Nach einem veränderten Gartenbereich den weiter verwendbaren Anteil eines alten Aufmaßes bestimmen — Scope the resurvey after fixed garden landmarks change.

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": {
      "alt_m2": "<alt_m2>",
      "beete_geaendert_m2": "<beete_geaendert_m2>",
      "weg_geaendert_m2": "<weg_geaendert_m2>",
      "beide_m2": "<beide_m2>",
      "gleiche_grundlage": "<gleiche_grundlage>"
    },
    "name": "maehroboter_uebernommener_garten_aenderungsflaechen"
  }
}

Input Schema

NameRequiredDescriptionDefault
alt_m2YesGemessene Gesamtfläche des bisherigen Aufmaßes.
beide_m2YesTeilfläche, die in beiden Angaben enthalten ist.
weg_geaendert_m2YesFläche mit verändertem Weg.
gleiche_grundlageYesAltes und neues Aufmaß beziehen sich auf dieselben Grundstücksabschnitte?
beete_geaendert_m2YesFläche mit geändertem Beetrand.

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, closed-world compute nature is covered structurally. The description adds that the tool scopes a resurvey after fixed landmarks change, but it never says what the result means when 'gleiche_grundlage' is false — the one behavior an agent most needs to know for a five-required-parameter computation.

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 with the trigger condition front-loaded and no filler. The English gloss is partly redundant with the German sentence, but it is short and aids disambiguation rather than padding.

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-required-parameter computation with no output schema, the definition should at least convey what the returned 'usable share' represents and how the overlap parameter affects it. It conveys the general intent adequately but leaves the output meaning and the effect of the boolean precondition unexplained.

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 every parameter is already documented in the schema, which sets the baseline at 3. The description's terms ('altes Aufmaß', 'veränderter Gartenbereich', 'feste Orientierungspunkte') loosely echo alt_m2 and the changed-area parameters but add no arithmetic or overlap semantics 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 concrete operation on a concrete resource: determine the still-usable share of an old survey ('weiter verwendbaren Anteil eines alten Aufmaßes') after a garden area changes. That is far more specific than the opaque tool name and an agent can tell it is a read-only area reconciliation rather than a mowing/sensor tool. It stops short of contrasting itself with any sibling name.

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 opening clause 'Nach einem veränderten Gartenbereich…' implies the triggering situation (a garden area has changed and the old measurement must be partly reused). There is no explicit when-not guidance, no prerequisites, and no alternative tool is named for the case where the old survey is entirely invalid.

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