Skip to main content
Glama

getecoback-raumklima

maehroboter_grundstueckskizze_nachbarflaeche_abgrenzen

Read-only

In einer Gartenskizze Fläche mit geklärter Nutzung von gemeinsam genutzter oder offener Fläche trennen — Keep shared or unresolved ground outside the candidate work area.

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": {
      "gesamt_m2": "<gesamt_m2>",
      "fremd_m2": "<fremd_m2>",
      "gemeinsam_ungeklaert_m2": "<gemeinsam_ungeklaert_m2>",
      "eigene_route_belegt": "<eigene_route_belegt>"
    },
    "name": "maehroboter_grundstueckskizze_nachbarflaeche_abgrenzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
fremd_m2YesDavon dokumentiert separat genutzte Fläche.
gesamt_m2YesBemaßte Fläche auf der aktuellen Gartenskizze.
eigene_route_belegtYesIst der Weg zur separat geklärten Fläche vor Ort geklärt?
gemeinsam_ungeklaert_m2YesDavon unabhängig abgegrenzte gemeinsam genutzte Fläche mit offener Absprache.

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, closed-world computation. The description adds the behavioral outcome that the shared/open ground is excluded from the candidate work area, but it says nothing about what is returned (a boundary, a derived area figure, a validation result) or how the boolean gating parameter changes behaviour.

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 short clauses with no filler, and the operative action ('trennen') plus the constraint are front-loaded. The bilingual duplication is a small redundancy but aids comprehension rather than obscuring it.

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?

With four required numeric/boolean inputs and no output schema, the description should at least indicate what the tool produces and how the four measures are consumed. It conveys the intent but leaves the result shape and the role of eigene_route_belegt unexplained, which is a meaningful gap for a derivation tool.

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 the schema already documents all four parameters, including the boolean 'eigene_route_belegt'. The description adds the concept of clarified versus unresolved ground, which loosely maps onto fremd_m2 and gemeinsam_ungeklaert_m2, but provides no meaning for the path-clarification flag or for how the values are combined.

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 concrete operation in German: separating area with clarified use from jointly used or open area within a garden sketch, plus an English restatement of the goal. That is a specific verb+resource, but it does not distinguish this from related garden-evaluation tools such as maehroboter_gartencheck, so the agent must infer the boundary from the parameter names.

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 second clause ('Keep shared or unresolved ground outside the candidate work area') gives an implied usage rule for the candidate work area, so the context of use is inferable. There is no explicit when-to-use versus sibling tools, no prerequisites, and no statement about when this step should be skipped.

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