BestRobotMower MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_robot_mowersB | List and filter robot lawn mowers from the BestRobotMower.co dataset. Filter by brand, navigation type, price, lawn coverage, slope handling and minimum score; sort by score, price, coverage or value. |
| get_robot_mowerA | Get the full spec sheet, sub-scores and cited sources for one robot lawn mower by model name or slug. |
| compare_robot_mowersA | Compare 2 to 4 robot lawn mowers side by side on price, navigation, coverage, slope, cutting specs and scores. |
| recommend_robot_mowerB | Recommend the best-fitting robot lawn mowers for a specific yard: give the lawn size and optionally slope, budget and whether obstacle avoidance is needed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: list (browse/filter), get (single full record), compare (2-4 side by side), and recommend (yard-specific matching). There is minimal risk of misselection since the resource+action combos don't overlap.
All four tools follow a consistent verb_noun pattern (list_robot_mowers, get_robot_mower, compare_robot_mowers, recommend_robot_mower). Plural/singular usage is predictable and readable.
Four tools is well-scoped for a read-only dataset server; each covers a distinct retrieval mode with no redundancy. Nothing feels missing or excessive for the stated purpose.
The query surface (browse, fetch, compare, recommend) fully covers a read-only dataset domain. Minor gap: no tool to enumerate available brands/navigation types/facets, though filters on list_robot_mowers allow agents to work around this.