Skip to main content
Glama

getecoback-climate-weather

maehroboter_steigungsprofil

Read-only

Gemessene Steigung mit der Vorgabe für genau diese Teilstrecke vergleichen — Compare measured grade with the exact limit for mowing area, boundary or passage.

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": {
      "rise_cm": "<rise_cm>",
      "horizontal_cm": "<horizontal_cm>",
      "limit_percent": "<limit_percent>",
      "matching_manual_limit": "<matching_manual_limit>"
    },
    "name": "maehroboter_steigungsprofil"
  }
}

Input Schema

NameRequiredDescriptionDefault
rise_cmYesHöhenunterschied über die kurze vermessene Strecke in Zentimetern.
horizontal_cmYesHorizontale Strecke in Zentimetern, nicht die diagonale Oberfläche.
limit_percentYesGrenze in Prozent laut Anleitung, sofern für diese Teilstrecke eindeutig dokumentiert.
matching_manual_limitYesGrenze gilt für diese Stelle, etwa Hauptfläche, Rand oder Passage, und exakt diese Ausführung?

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 readOnlyHint and openWorldHint annotations already establish a safe, closed-domain operation. The description adds that this is a comparison against an exact manual limit for a specific subsection, but it does not describe return behavior or failure conditions. No annotation contradiction is present.

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 compact and front-loads the comparison purpose. The German and English versions duplicate the same meaning, which is functionally redundant but very brief, so it remains efficient overall.

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?

This is a simple read-only calculation with four fully documented required parameters and no output schema. The description says what is compared but does not indicate the form of the result, such as whether the slope passes, fails, or exceeds the limit. That is a meaningful gap given the absence of an output schema.

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 all four parameters are already documented in the input schema. The description restates the core comparison in natural language but does not add new syntax, units, or interpretation beyond the schema. Baseline 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 comparison action: measured grade versus the exact limit for a mowing area, boundary, or passage. The verb and resource are clear. It does not explicitly distinguish this tool from sibling tools, so a 4 rather than a 5.

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 description implies the tool is used when checking a measured slope against a documented mowing-area limit. It does not explicitly state when to use it versus alternatives, nor does it give exclusions or prerequisites beyond mentioning the exact subsection.

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