Skip to main content
Glama

Citybikes

by io.github.pipeworx-io
OverviewAdmin

Citybikes Networks Near

citybikes_networks_near
Read-onlyIdempotent

Find bike-share networks near a lat/lon: "bike share near me", "find bike rental network by location", "citybikes nearby coordinates". Returns the closest networks sorted by distance with their id, name, city, country, and distance_km. If none fall within radius_km, returns count:0 plus a note naming the single nearest network beyond the radius. To then get live stations and free bikes for a returned network, call get_network with its id. Example: Göttingen (latitude 51.53, longitude 9.93) → nextbike-kassel ~39.5km away.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax networks to return, 1-20 (default 5)
latitudeYesLatitude of the search center (e.g. 51.53)
longitudeYesLongitude of the search center (e.g. 9.93)
radius_kmNoSearch radius in kilometers (default 50; bike networks are sparse, so the nearest city may be 30km+ away)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "latitude": 51.53,
+    "longitude": 9.93
+  },
+  {
+    "latitude": 40.7128,
+    "limit": 10,
+    "longitude": -74.006,
+    "radius_km": 30
+  }
+]
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnly, openWorld, idempotent), the description discloses concrete behavioral details: results are sorted by distance, include specific fields, and the fallback behavior when no network is within radius_km (returns count:0 plus a note naming the nearest network). This exceeds what annotations alone convey.

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 front-loaded with the core purpose, includes a compact list of return fields, gives a fallback detail, provides a cross-reference to a sibling tool, and ends with a concrete example. Every sentence serves a purpose and the length is appropriate for the tool's complexity.

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?

With no output schema, the description fully specifies the return shape (sorted networks, fields, count:0 + note) and provides operational context (radius caveat, example output). It also tells the user the next step (get_network) for live data, making it self-sufficient for the agent to select and invoke 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 baseline is 3. The description adds value by clarifying output implications (distance_km, count:0 fallback), the practical radius default context ('bike networks are sparse'), and the relationship between parameters and results. It does not introduce syntax conflicts.

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 opens with a clear, specific verb+resource statement ('Find bike-share networks near a lat/lon') and provides natural-language query examples. It distinguishes itself from sibling tools like get_network and list_networks by focusing on location-based proximity search.

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 clearly implies when to use this tool (when you have coordinates and want nearby networks) and explicitly names the alternative for follow-up: 'call get_network with its id' for live stations. It does not enumerate all sibling exclusions, but the context is unambiguous.

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

All Citybikes toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources