BikesAndThat

List UK bike parks

list_bike_parks

Read-onlyIdempotent

List UK mountain bike parks from BikesAndThat. Filter by location text (e.g. 'Wales'), trail difficulty (minimum blue/red/black counts, pro lines), uplift (available or type such as 'van'), or distance from a latitude/longitude. When coordinates are given, results include distance_miles and are sorted closest first.

Input Schema

Name	Required	Description
`limit`	No	Max rows to return. Default 100.
`latitude`	No	Origin latitude for distance search.
`longitude`	No	Origin longitude for distance search.
`uplift_type`	No	Substring to match against uplift type, e.g. 'van', 'gondola', 'chairlift'.
`radius_miles`	No	Only return parks within this many miles of latitude/longitude.
`featured_only`	No	If true, return only featured parks.
`has_pro_lines`	No	If true, only parks with at least one pro line.
`min_red_trails`	No	Minimum number of red trails.
`min_blue_trails`	No	Minimum number of blue trails.
`min_black_trails`	No	Minimum number of black trails.
`uplift_available`	No	True for parks with an uplift service; false for push-up/pedal-only parks.
`location_contains`	No	Case-insensitive substring to match against the park's location field.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 20, 2026

addedInput schema / properties / featured_only / description
```
Added value: +"If true, return only featured parks."
```

addedInput schema / properties / has_pro_lines

Added value: +{
+  "description": "If true, only parks with at least one pro line.",
+  "type": "boolean"
+}

addedInput schema / properties / latitude

Added value: +{
+  "description": "Origin latitude for distance search.",
+  "maximum": 90,
+  "minimum": -90,
+  "type": "number"
+}

addedInput schema / properties / limit / description
```
Added value: +"Max rows to return. Default 100."
```

addedInput schema / properties / location_contains / description

Added value: +"Case-insensitive substring to match against the park's location field."

addedInput schema / properties / longitude

Added value: +{
+  "description": "Origin longitude for distance search.",
+  "maximum": 180,
+  "minimum": -180,
+  "type": "number"
+}

addedInput schema / properties / min_black_trails

Added value: +{
+  "description": "Minimum number of black trails.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / min_blue_trails

Added value: +{
+  "description": "Minimum number of blue trails.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / min_red_trails

Added value: +{
+  "description": "Minimum number of red trails.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / radius_miles

Added value: +{
+  "description": "Only return parks within this many miles of latitude/longitude.",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}

addedInput schema / properties / uplift_available

Added value: +{
+  "description": "True for parks with an uplift service; false for push-up/pedal-only parks.",
+  "type": "boolean"
+}

addedInput schema / properties / uplift_type

Added value: +{
+  "description": "Substring to match against uplift type, e.g. 'van', 'gondola', 'chairlift'.",
+  "type": "string"
+}

First observedOct 15, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent and closed-world behavior, so the description's added value is the output behavior: when coordinates are supplied, results carry distance_miles and are sorted closest-first. That is real behavioral disclosure beyond the structured fields, though rate limits, pagination beyond the limit param, and result shape are not covered.

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, no filler. The core purpose leads, the filter enumeration follows, and the distance/sort caveat closes — an efficient structure for a 12-parameter tool.

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?

With no output schema, the description partially compensates by describing the distance_miles field and sort order, and the schema itself documents limit and all filters. It does not describe the overall record shape or result envelope, but nothing needed to invoke the tool correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine semantic value by distinguishing the two uplift filters ('available or type such as van') and clarifying that difficulty filters are minimum counts rather than exact matches. That maps directly onto uplift_available vs uplift_type and the min_*_trails params.

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 and resource with scope: 'List UK mountain bike parks from BikesAndThat'. The plural 'list' naturally separates it from the singular get_bike_park sibling, though the description never names an alternative explicitly, which keeps it just short of 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 Guidelines4/5

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

The description enumerates the four filter modes (location text, trail difficulty thresholds, uplift, distance) with concrete examples like 'Wales' and 'van', which tells an agent exactly what this tool is for. It stops short of stating when to prefer get_bike_park or search_bike_shops instead, so no explicit exclusions.

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

All BikesAndThat 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?