flow-planner
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| statusC | BRouter reachability, region, stop-model weight set, flow index size and DEM coverage. |
| start_brouterA | Start the local BRouter server (scripts/run_brouter.sh serve) if it is not reachable; waits up to 60 s. |
| geocodeB | Look up an Irish place name (Nominatim). Returns candidates with name and lat,lon. |
| plan_routeA | Plan routes. mode: loop | out_and_back | one_way. start/end: 'lat,lon' or a place name (geocoded; the resolved place is echoed). Loops and out-and-backs need length_km (+-10%) or min_km and max_km; one_way needs end and ignores length. objective: flow (fewest stops/turns) | climb | flat. return_mode: same | free. settings: optional dict from list_presets (e.g. turn_cost, lane_bonus, weights; main_road_penalty 1..5 multiplies the cost of primary, secondary and trunk roads, 2.5 = 'quiet roads' preset). Loops take 30-60 s. Returns a markdown table of ranked routes (use the ids with route_details / export_gpx) plus plan notes. |
| route_detailsB | Explain a planned route: km by road class, cycle-infrastructure km, stop events, climbs, turns. |
| export_gpxB | Write a planned route as GPX 1.1 (with elevation) into out_dir (must exist; absolute or ~). |
| list_presetsA | Settings presets (straight & lanes, plain flow, climb, flat) as dicts: pass |
| pick_pointsA | Ask the user to click 1 or 2 points on the planner map (opens the browser at the planner web page, which
needs |
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 8 tools
Each tool has a clearly distinct role in the route-planning workflow: planning, inspecting, exporting, presets, point picking, geocoding, status, and starting BRouter. There is no meaningful overlap; plan_route returns route IDs while route_details and export_gpx consume them.
Most names follow a predictable snake_case verb_noun or noun pattern (route_details, export_gpx, list_presets, pick_points, start_brouter, plan_route). A few deviations like status and geocode are single-word but still clear and readable.
Eight tools is well-scoped for a route-planning server, with each tool covering a necessary step from setup to output. No tool feels redundant or missing from the count.
The surface covers the core lifecycle: discover places, configure settings, plan routes, inspect details, and export GPX. Minor gaps exist around managing multiple saved routes or re-inspecting previously planned routes beyond the immediate result set.