Skip to main content

bestrobotmower-mcp

by io.github.yumaheymans

Overview Discussions Admin

List robot mowers

list_robot_mowers

List and filter the robot lawn mowers in the BestRobotMower.co dataset by brand, navigation type, price, lawn-area coverage, slope handling and score. Returns models ranked by the 0-5 BestRobotMower Score (highest first).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`brand`	No	Filter by brand, case-insensitive substring (e.g. 'Mammotion', 'Segway', 'Husqvarna').
`limit`	No	Max models to return (default 10, max 76, the whole catalog).
`min_score`	No	Only models with a BestRobotMower Score at or above this value (0-5).
`navigation`	No	Filter by navigation type, case-insensitive substring (e.g. 'RTK', 'satellite', 'vision', 'wire').
`max_price_usd`	No	Only models at or below this USD price.
`min_slope_pct`	No	Only models rated for at least this slope, in percent grade.
`min_lawn_area_m2`	No	Only models that cover at least this lawn area in square metres.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 3, 2026

changedInput schema / properties / limit / description

Previous value: -"Max models to return (default 10, max 70, the whole catalog)."New value: +"Max models to return (default 10, max 76, the whole catalog)."

changedInput schema / properties / limit / maximum
```
Previous value: -70New value: +76
```

Changed2 schema fields changedOct 1, 2026

changedInput schema / properties / limit / description

Previous value: -"Max models to return (default 10, max 57, the whole catalog)."New value: +"Max models to return (default 10, max 70, the whole catalog)."

changedInput schema / properties / limit / maximum
```
Previous value: -57New value: +70
```

Changed2 schema fields changedOct 1, 2026

changedInput schema / properties / limit / description

Previous value: -"Max models to return (default 10, max 55, the whole catalog)."New value: +"Max models to return (default 10, max 57, the whole catalog)."

changedInput schema / properties / limit / maximum
```
Previous value: -55New value: +57
```

Changed2 schema fields changedOct 1, 2026

changedInput schema / properties / limit / description

Previous value: -"Max models to return (default 10, max 48, the whole catalog)."New value: +"Max models to return (default 10, max 55, the whole catalog)."

changedInput schema / properties / limit / maximum
```
Previous value: -48New value: +55
```

Changed2 schema fields changedOct 1, 2026

changedInput schema / properties / limit / description

Previous value: -"Max models to return (default 10, max 39, the whole catalog)."New value: +"Max models to return (default 10, max 48, the whole catalog)."

changedInput schema / properties / limit / maximum
```
Previous value: -39New value: +48
```

Changed2 schema fields changedSep 28, 2026

changedInput schema / properties / limit / description

Previous value: -"Max models to return (default 10, max 23)."New value: +"Max models to return (default 10, max 39, the whole catalog)."

changedInput schema / properties / limit / maximum
```
Previous value: -23New value: +39
```

First observedSep 21, 2026

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full disclosure burden. It usefully reveals the ordering behavior (ranked by 0-5 BestRobotMower Score, highest first), which is not derivable from the schema. It omits that this is a read-only operation and says nothing about the default 10-result cap silently truncating output, which is a real behavioral risk for an agent expecting the full catalog.

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

Conciseness5/5

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

Two sentences, zero waste. The scope and filterable dimensions come first and the return ordering is front-loaded in the second sentence, so the most decision-relevant facts are read immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with no annotations and no output schema, the description covers purpose, filterable fields, and result ordering, which is enough to call it correctly. The one meaningful gap is not flagging the default result cap, which the agent would otherwise have to discover in the 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 description coverage is 100%, so the schema already documents all seven filters including substrings, ranges, and defaults. The description only restates the filter categories at a coarser level, adding no syntax or format detail beyond what the schema provides; baseline 3 applies.

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

Purpose5/5

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

The description states a specific verb ('List and filter') plus the exact resource (robot lawn mowers in the BestRobotMower.co dataset) and enumerates the filterable dimensions. This makes it naturally distinguishable from get_robot_mower (single model), compare_robot_mowers (side-by-side), and recommend_robot_mower (advisory), without needing to name them.

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?

Usage is implied by the filter dimensions and the ranking statement, so an agent can infer this is the browse/search entry point. However, there is no explicit guidance on when to prefer this over compare_robot_mowers or recommend_robot_mower, and no stated exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All bestrobotmower-mcp tools Inspect

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources