Skip to main content
Glama

Shared bikes, e-scooters and cars near a point

get_shared_vehicles_nearby
Read-only

Find available shared vehicles and docking stations near WGS84 coordinates, filtered by vehicle type and radius, with provider, distance, and published battery range.

Instructions

Live shared-mobility availability near WGS84 coordinates from sharedmobility.ch (SFOE national aggregator: PubliBike, Donkey Republic, Bolt, Voi, Tier, Mobility car sharing, carvelo cargo bikes, …). Returns free-floating vehicles and docking stations (with vehicles/docks available) sorted by distance, each with provider name, vehicle types, distance_m and battery range where published. Filter with vehicle_type: bike | e-bike | cargo_bike | scooter | moped | car. Example: {lat: 47.3779, lon: 8.5403, radius_m: 300, vehicle_type: 'scooter'} (Zürich HB). Use geocode first to turn an address into coordinates.

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": "get_shared_vehicles_nearby"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesWGS84 latitude, e.g. 46.9488 (Bern)
lonYesWGS84 longitude, e.g. 7.4391
kindNoFree-floating vehicles, docking stations, or bothall
limitNo
radius_mNoSearch radius in metres (default 500)
vehicle_typeNoOnly this kind of vehicle ('bike' = non-electric)
only_availableNoHide reserved/disabled vehicles and empty stations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real behavioral value beyond that: the data is live, results are sorted by distance, both free-floating vehicles and docking stations are returned, and each item carries provider, vehicle types, distance_m and battery range where published.

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?

The key facts — live availability, geographic scope, return shape — are front-loaded, and the example is placed at the end where it aids invocation. The parenthetical provider roster ('PubliBike, Donkey Republic, Bolt, Voi, Tier, …') is somewhat longer than needed but does convey coverage breadth.

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 carries the burden of explaining returns and does so adequately: sorted-by-distance list with provider, vehicle types, distance_m and battery range. It also implicitly signals Swiss coverage via the aggregator and coordinate bounds. Minor gaps remain around pagination and what happens when no vehicles are found.

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 86%, so the schema already documents almost every parameter, including the vehicle_type enum and the 'bike = non-electric' clarification. The description's example demonstrates how parameters combine but adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 states a specific verb and resource — 'live shared-mobility availability near WGS84 coordinates' — and names the underlying source (sharedmobility.ch, SFOE aggregator) along with the providers it covers. An agent can immediately distinguish this from generic point-query or EV-charger siblings by the vehicle_type enum and the provider list.

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?

It gives a concrete prerequisite: 'Use geocode first to turn an address into coordinates', and supplies a worked example showing lat/lon/radius/vehicle_type together. It does not explicitly state when to prefer an alternative (e.g. list_shared_mobility_providers for provider metadata), so it falls short of full when/when-not guidance.

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

Deploy Server

Other Tools