Skip to main content
Glama

getecoback-climate-weather

maehroboter_maehfenster

Read-only

Beobachtete Mähdauer auf verfügbare beaufsichtigte Zeitfenster verteilen — Estimate whether a mowing plan fits user-supplied permitted and supervised time windows.

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": {
      "target_m2": "<target_m2>",
      "observed_m2": "<observed_m2>",
      "observed_min": "<observed_min>",
      "window_min": "<window_min>",
      "separable": "<separable>"
    },
    "name": "maehroboter_maehfenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
separableYesAufteilen auf mehrere ungefähr gleichartige Teilflächen möglich und laut Anleitung zulässig?
target_m2YesZielfläche des betrachteten Arbeitsgangs.
window_minYesNetto nutzbares Zeitfenster in Minuten. Sperrzeiten und Pausen bereits abziehen.
observed_m2YesFläche einer bereits beobachteten vergleichbaren Runde.
observed_minYesDauer dieser Runde inklusive unvermeidlicher Unterbrechungen in Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 and locality profile is covered. The description adds that the tool estimates/distributes duration across windows, but it does not disclose key assumptions such as how separability affects the estimate or what the result contains.

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?

The description is a single compact sentence with the main purpose front-loaded. The German and English formulations are slightly duplicative, but neither is wasteful or confusing.

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?

All parameters are documented in the schema and the read-only annotation is supplied, so the core call is understandable. However, with no output schema and no explanation of return values or calculation assumptions, the description leaves some gaps for a multi-parameter estimation 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 input schema already documents all five parameters well. The description mentions observed duration and supervised time windows but adds no parameter-level meaning beyond the schema, so the baseline score of 3 is appropriate.

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 specific estimation task: checking whether a mowing plan fits permitted and supervised time windows, with observed mowing duration distributed across available windows. It clearly conveys the verb and resource, but it does not explicitly differentiate this tool from sibling tools such as the garden check or slope profile.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit when-to-use guidance, prerequisites, or comparison with alternatives. It implies the context of checking schedule feasibility, but an agent gets no instruction on when to choose this tool over siblings.

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