Bay Wheels MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Bind host | 0.0.0.0 |
| PORT | No | Server port | 8000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_nearest_bikeA | Find the nearest dock with at least N available bikes, or free bike locations if N=1. Args: latitude: The latitude of the search location. longitude: The longitude of the search location. count: The number of bikes needed (default 1). bike_type: Optional type of bike ('electric_bike' or 'classic_bike'). If None, any type. |
| find_nearest_dock_spacesA | Find the nearest dock with at least N available return spaces. Args: latitude: The latitude of the search location. longitude: The longitude of the search location. count: The number of spaces needed (default 1). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one locates available bikes for pickup, the other locates available return spaces. There is no overlap or ambiguity between them.
Both tool names follow the consistent pattern 'find_nearest_' followed by the object ('bike' or 'dock_spaces'). This creates a predictable and coherent naming convention.
With only two tools, the server feels thin but is appropriately scoped for a simple find-nearest utility. It is borderline, as it might benefit from additional tools like station list or trip planning, but it is not excessive.
The pair covers the two core needs of a bike-sharing user: finding bikes to rent and finding spaces to return. Minor gaps exist (e.g., station details or real-time status), but for the apparent minimal scope, it is mostly complete.