Skip to main content
Glama
Sign In

BikeTheRail

by org.biketherail
OverviewDiscussionsAdmin

Trails near a point

trails_near
Read-onlyIdempotent

Trails within a radius of a latitude and longitude, nearest first, with the distance to the closest point of each trail. For a town or address, pass its coordinates. Optional filters as in search_trails.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "trails_near"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude in decimal degrees.
lonYesLongitude in decimal degrees (negative in the United States).
kindNorail: on a former railway; trolley: an old streetcar or interurban line; canal_towpath: beside a canal; greenway: a car-free path not on a railbed.
limitNoHow many trails to return (1-50).
surfaceNoTrail surface. crushed_stone is packed stone dust, good for most bikes.
min_milesNoShortest trail length, in miles.
radius_milesNoSearch radius in miles (up to 100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavior beyond that: results are ordered nearest-first and each carries a distance to the trail's closest point, which is not derivable from annotations or schema.

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?

Three short sentences, front-loaded with the core semantics (radius, ordering, distance) before the practical coordinate tip and the filter cross-reference. Nothing is padded.

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?

Seven parameters are fully documented in the schema and the annotations carry the safety profile; the only thing structured data cannot supply — result ordering and the computed distance field — is stated explicitly. An agent has everything needed to call this correctly.

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. The description still adds meaning: it tells the agent lat/lon may be sourced from a town or address, and that the optional filters mirror search_trails, which frames kind/surface/min_miles as the familiar filter set rather than unexplained knobs.

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?

States a specific operation on a specific resource with scope: trails within a radius of a lat/lon, ordered nearest-first. It also discloses the distinguishing return detail (distance to the closest point of each trail), which separates it from get_trail (single trail) and from the filter-driven search_trails.

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

Usage Guidelines3/5

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

"For a town or address, pass its coordinates" is actionable input guidance, and referencing "filters as in search_trails" hints that sibling handles non-proximity queries. However, it never explicitly says when to choose this over search_trails or when a proximity search is the wrong tool.

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

All BikeTheRail toolsInspect
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