cyclesite-mcp-server

Search by location

search_by_location

Read-onlyIdempotent

Find Cyclesite listings within a radius of a UK town, city or postcode district (the first half of a postcode, e.g. 'BS1', 'M20'). A full postcode is cut to its district; coordinates are not accepted. Radius capped at 50 miles. Returns up to 10 listings ordered by distance, rounded to the mile, and searchedFrom naming the place measured from. Live UK marketplace data. Example: 'used bikes within 25 miles of Leicester' or 'road bikes near LE10'.

Input Schema

Name	Required	Description
`limit`	No	1-10, default 5.
`place`	Yes	UK town or city name (e.g. 'Bristol'), or a postcode district (e.g. 'BS1').
`category`	No
`maxPrice`	No
`radiusMiles`	No	Search radius in miles (1-50, default 25).

Output Schema

Name	Required	Description
`listings`	Yes
`attribution`	Yes	Citation string for the data in this result.
`resultsCount`	Yes
`searchedFrom`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

changedOutput schema / properties / attribution / description

Previous value: -"Citation string — include verbatim when surfacing data."New value: +"Citation string for the data in this result."

Changed5 schema fields changedOct 28, 2026

removedInput schema / properties / lat

Removed value: -{
-  "description": "Latitude (UK only, 49.5–61.0).",
-  "type": "number"
-}

removedInput schema / properties / lng

Removed value: -{
-  "description": "Longitude (UK only, -8.5–2.0).",
-  "type": "number"
-}

addedInput schema / properties / place

Added value: +{
+  "description": "UK town or city name (e.g. 'Bristol'), or a postcode district (e.g. 'BS1').",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "lat",
-  "lng"
-]New value: +[
+  "place"
+]

addedOutput schema / properties / searchedFrom
```
Added value: +{
+  "type": "string"
+}
```

Changed3 schema fields changedSep 21, 2026
- addedOutput schema / properties / listings / items / properties / distanceMiles
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / listings / items / properties / listingId
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / listings / items / properties / slug
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

Changed1 schema field changedAug 4, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "road",
-  "mtb",
-  "gravel",
-  "hybrid",
-  "ebike",
-  "kids",
-  "bmx",
-  "folding",
-  "city",
-  "touring",
-  "triathlon",
-  "track",
-  "cyclocross",
-  "cargo",
-  "other"
-]New value: +[
+  "road",
+  "mtb",
+  "gravel",
+  "hybrid",
+  "ebike",
+  "kids",
+  "bmx",
+  "folding",
+  "city",
+  "touring",
+  "triathlon",
+  "track",
+  "cyclocross",
+  "cargo",
+  "adaptive",
+  "other"
+]

Changed8 schema fields changedJun 28, 2026
- addedOutput schema / properties / listings / items / properties / delivery
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / listings / items / properties / ebikeBatteryWh
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / listings / items / properties / ebikeMotor
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / listings / items / properties / frameMaterial
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / listings / items / properties / groupset
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / listings / items / properties / imageUrl
```
Added value: +{
+  "format": "uri",
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / listings / items / properties / negotiable
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / listings / items / properties / wheelSize
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed6 schema fields changedMay 28, 2026
- changedOutput schema / properties / listings / items / properties / brand / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / listings / items / properties / city / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / listings / items / properties / frameSize / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / listings / items / properties / model / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / listings / items / properties / url / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / listings / items / properties / year / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```

Changed1 schema field changedMay 22, 2026

addedOutput schema / properties / listings / items / properties / offer

Added value: +{
+  "description": "UCP/ACP-shaped commerce signal for this listing.",
+  "properties": {
+    "availability": {
+      "type": "string"
+    },
+    "itemCondition": {
+      "type": "string"
+    },
+    "price": {
+      "type": "number"
+    },
+    "priceCurrency": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedMay 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real behavioral context: radius capped at 50 miles, results capped at 10 and ordered by distance, distances rounded to the mile, and a searchedFrom field naming the measured place. Some of that overlaps the output schema, which is why it is not a 5.

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?

Front-loads the core purpose, then constraints (postcode handling, radius cap, result cap), then examples — a logical order with little waste. The examples sentence is a mild luxury but does encode valid query shapes.

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

Completeness5/5

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

For a 5-parameter filtered search with annotations and an output schema, the description covers the hard parts an agent would otherwise get wrong: accepted place formats, the no-coordinates rule, radius ceiling and result ceiling. Only the filtering semantics of `category` and `maxPrice` are left to the schema, which is a reasonable division of labor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds meaning beyond the 60%-covered schema: it explains that a full postcode is truncated to its district, that a district like 'BS1' or 'M20' is the expected form for `place`, and that radius is capped at 50 miles. It says nothing about `category` or `maxPrice`, leaving those to the schema.

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?

States a specific verb+resource ('Find Cyclesite listings') plus a precise geographic scope ('within a radius of a UK town, city or postcode district'). An agent can tell this is a geo-radius listing search, but no sibling such as search_bikes or search is named, so differentiation from keyword search is left implicit.

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

Usage Guidelines4/5

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

Gives concrete usage examples ('used bikes within 25 miles of Leicester', 'road bikes near LE10') and an explicit exclusion ('coordinates are not accepted'), which steers the agent away from a common wrong input. It never names an alternative tool for non-geographic searching, so the when-not-to-use-this-tool routing is incomplete.

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

All cyclesite-mcp-server tools Inspect

Try in Browser

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

Need Help?