boston-harbor-ferries
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APRS_API_KEY | Yes | Your API key from aprs.fi | |
| APRS_CACHE_TTL_SECONDS | No | Cache TTL in seconds (default 120) | 120 |
| APRS_MAX_REQUESTS_PER_MINUTE | No | Maximum API requests per minute (default 10) | 10 |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| track_ferryB | Get current position and status of a Boston Harbor ferry by MMSI number |
| track_all_ferriesA | Get current positions of all Boston Harbor commuter ferries |
| list_ferriesA | List all known Boston Harbor commuter ferries with their details |
| get_ferry_routesB | Get information about ferry routes and schedules |
| clear_cacheA | Clear all cached ferry position data |
| get_harbor_weatherA | Get current weather conditions for Boston Harbor from nearby CWOP station (EW2727) |
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 6 tools
Tool purposes are mostly distinct: track_ferry is singular position lookup, track_all_ferries is plural positions, list_ferries is static fleet details, and routes/weather/cache are separate concerns. There is minor potential confusion between list_ferries and track_all_ferries, but descriptions clarify the difference.
All tool names follow a clear verb_noun pattern: track, list, get, clear. The naming is consistent and predictable, with no style mixing or vague verbs.
Six tools is well-scoped for a ferry information server. Each tool serves a clear purpose without redundancy, covering tracking, fleet information, routes, weather, and cache management.
The tool set covers the core ferry domain well: list fleet, track individual/all ferries, get routes and schedules, and check weather. Minor gaps exist such as no terminal status or service alerts, but these are not obvious dead ends for basic ferry tracking use cases.