DriveBC MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_highway_conditionsA | Get current conditions, incidents, and closures for a specific BC highway. Returns active events including construction, accidents, weather conditions, and road closures. |
| get_regional_conditionsB | Get road conditions and events for a specific BC region. Useful for planning trips within a geographic area. |
| get_road_closuresC | List all current road closures and major restrictions across BC or filtered by region/highway. Includes full closures, lane closures, and significant restrictions. |
| get_weather_alertsC | Get active weather alerts, incidents, and road condition warnings across BC. Includes winter conditions, avalanche warnings, fog advisories, and weather-related incidents. |
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 4 tools
The tools are mostly distinct, with each focusing on a specific aspect of road conditions: highway-specific, regional, closures, and weather alerts. However, there is some overlap between get_highway_conditions and get_road_closures, as both could include closure information, which might cause minor confusion for an agent. The descriptions help clarify the distinctions, but the boundaries are not perfectly clear.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., get_highway_conditions, get_regional_conditions). This predictability makes it easy for an agent to understand and use the tools without confusion, as there are no deviations in naming conventions.
With 4 tools, the server is well-scoped for providing road condition information in BC. Each tool serves a distinct purpose, and the count is appropriate for the domain, avoiding both overcomplication and undercoverage. This aligns with typical MCP server tool counts for focused services.
The tool surface covers key aspects of road conditions, including specific highways, regions, closures, and weather alerts, which supports planning and monitoring. A minor gap exists in not having tools for historical data or predictive analytics, but agents can work around this with the provided tools for current conditions. Overall, it offers good coverage for the stated purpose.