search_bike_shopsSearch MTB bike shops in the UK by town, region, or country. Returns shop name, location, website, and whether a workshop is available.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max rows to return. Default 50. | |
| query | No | Substring to match against shop_name, town, or region. | |
| country | No | Country filter e.g. 'England', 'Scotland', 'Wales'. | |
| workshop_only | No | If true, only shops offering a workshop. |
Changes observed during successful MCP inspections.
Input schema / properties / country / descriptionAdded value: +"Country filter e.g. 'England', 'Scotland', 'Wales'."Input schema / properties / limit / descriptionAdded value: +"Max rows to return. Default 50."Input schema / properties / query / descriptionAdded value: +"Substring to match against shop_name, town, or region."Input schema / properties / workshop_only / descriptionAdded value: +"If true, only shops offering a workshop."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish readOnly, idempotent, and closed-world semantics, so safety is covered. The description adds genuine value beyond those annotations by disclosing the returned fields (name, location, website, workshop availability) — important because no output schema exists. It stops short of describing result counts or pagination behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, zero padding: the first states the action and filter axes, the second states the return shape. Both sentences earn their place and the key scoping information is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description carries the return-value burden and does so adequately, and the 100%-covered input schema handles parameter detail. The only shortfall is the absence of any note on result volume, default limits, or empty-result behavior for a search tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so all four parameters are already documented in the schema with defaults, bounds, and matching semantics. The description's mention of town/region/country and workshop availability echoes that information without adding new syntax or format detail, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a specific verb+resource+scope: "Search MTB bike shops in the UK," and even names the filterable dimensions (town, region, country). It is clearly distinguishable from the bike-park siblings, though it never explicitly contrasts its search semantics with them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
"By town, region, or country" implies the supported lookup contexts, so usage is inferable. However, there is no when-to-use framing, no exclusions, and no mention of the sibling tools (e.g. use list_bike_parks for parks), leaving routing guidance implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.