Skip to main content
Glama

getecoback-climate-weather

rasenroboter_maehende_teilflaechen_uebergabe

Read-only

Nach einer beendeten beaufsichtigten Runde Restflächen für die nächste Planung bezeichnen — Separate fully, partly and unobserved areas after one outing.

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": {
      "nord": "<nord>",
      "mitte": "<mitte>",
      "sued": "<sued>",
      "gleiche_kartengrenze": "<gleiche_kartengrenze>"
    },
    "name": "rasenroboter_maehende_teilflaechen_uebergabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
nordYesBeobachteter Abschluss auf der bezeichneten Nordfläche.
suedYesBeobachteter Abschluss auf der bezeichneten Südfläche.
mitteYesBeobachteter Abschluss auf der mittleren Fläche.
gleiche_kartengrenzeYesStimmen die bezeichneten Flächen mit dem eigenen aktuellen Aufmaß überein?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 safety profile is covered. The description adds the useful sequencing context (post-round, pre-next-planning) but does not say what the separation produces, whether the result is stored or returned, or how 'unbekannt' areas are treated downstream — mildly at odds with the word 'bezeichnen', which could suggest a write.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the trigger, which is good. However, the German/English duplication is pure redundancy for an agent and the em-dash construction reads as two restatements rather than one precise sentence.

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 no output schema, the description should clarify what the agent receives back from a classification call, and it does not. All four required parameters are documented in the schema, so nothing critical is missing, but the tool's result contract is left fully implicit.

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 the three enums are self-documenting, so the schema carries the parameter burden. The description only paraphrases the enum triad ('fully, partly and unobserved') and adds nothing about 'gleiche_kartengrenze', which is the one parameter whose consequence is least obvious.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names an act ('Restflächen ... bezeichnen' / 'Separate fully, partly and unobserved areas') and a trigger point ('nach einer beendeten beaufsichtigten Runde'), so the general intent is graspable. But the verb is abstract — it is unclear whether the tool records a classification, produces a summary, or merely validates input — and no sibling is referenced to disambiguate it from the other 'uebergabe' tools.

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?

One concrete precondition is given: it applies after a completed supervised run, and the output feeds the next planning cycle. There is no statement of when NOT to use it, no alternative tool named, and no guidance on what to do if no supervised round has occurred.

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