Skip to main content
Glama

cyclesite-mcp-server

search_by_location

Read-onlyIdempotent

Find Cyclesite listings within a radius of a UK location (lat/lng). Radius capped at 50 miles. Returns up to 10 listings ordered by distance. Live UK marketplace data. Example: 'used bikes within 25 miles of LE10 0AA' (geocode the postcode first, then call this).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesLatitude (UK only, 49.5–61.0).
lngYesLongitude (UK only, -8.5–2.0).
limitNo1-10, default 5.
categoryNo
maxPriceNo
radiusMilesNoSearch radius in miles (1-50, default 25).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
listingsYes
attributionYesCitation string — include verbatim when surfacing data.
resultsCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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"
      +  ]
      +}
  2. Changed1 schema field changed
    • 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"
      +]
  3. Changed8 schema fields changed
    • 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"
      +  ]
      +}
  4. Changed6 schema fields changed
    • 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"
      +]
  5. Changed1 schema field changed
    • 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"
      +}
  6. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds valuable behavioral context: radius cap (50 miles), max results (10), distance ordering, live data, and the prerequisite to geocode first. This goes beyond annotations and helps the agent set expectations.

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?

The description is two sentences plus an example, with no wasted words. It front-loads the core purpose, then adds constraints, and finishes with a practical example. Every sentence contributes to understanding the 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?

Given the tool's complexity (6 parameters, 2 required) and the presence of an output schema, the description covers the essential behavior, constraints, and usage example. It does not mention error handling or edge cases, but for a read-only tool with strong annotations, this is sufficient.

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 coverage is 67%, with lat, lng, limit, and radiusMiles described. The description mentions the radius cap and result limit but does not add new meaning to parameters beyond what the schema provides. Since coverage is moderate but not low, the description is not required to compensate heavily; it adds minimal extra value.

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 clearly states the verb 'Find', the resource 'Cyclesite listings', and the specific scope 'within a radius of a UK location (lat/lng)'. It also adds distinguishing constraints like radius cap and return limit, making it distinct from sibling search tools. The example further clarifies the intended use case.

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 provides a concrete example ('used bikes within 25 miles of LE10 0AA') and instructs to geocode the postcode first, implying when this tool is appropriate. However, it does not explicitly mention alternatives or when not to use it, leaving some inference required.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources