GBFS France
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_networksA | Find docked bike-share networks by city, area or name. Returns network ids for nearby_stations and get_station, plus matching networks that are not supported and why. |
| nearby_stationsA | Nearest stations of one network to a point, with live bikes, e-bikes and free docks. Get network_id from search_networks first. |
| get_stationB | Live status of one station: bikes, e-bikes, free docks and whether it rents or accepts returns. |
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 3 tools
Each tool has a distinct scope: network discovery, single-station status, and nearby-station lookup. The only mild overlap is spatial search (search_networks by area vs. nearby_stations), but the descriptions clarify the network-vs-station granularity and prerequisite network_id.
search_networks and get_station follow a clear verb_noun pattern, while nearby_stations is an adjective_noun phrase. The deviation is minor and still readable, since all names are snake_case and intuitively describe their action or result.
Three tools is well-scoped for a focused read-only GBFS France server. Each tool covers a distinct need—network discovery, station status, and proximity lookup—without bloat or missing obvious companions.
The surface covers network search and live station status/proximity, but there are notable gaps such as station lookup by name or id without relying on nearby search, listing all stations in a network, and retrieving network-level metadata. These gaps may force workarounds for common queries.