ttc-mcp
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_fareA | The current TTC fare table (adult/senior/youth/child by payment type) plus the 2-hour transfer rule. Fares are a flat, hand-maintained table — TTC publishes no machine-readable fare data. Optionally filter by category and/or fare_type. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| fares | The full TTC fare table plus the 2-hour transfer rule — the get_fare tool's DTO. |
TDQS
Scored across 1 tool
With only one tool, there is no risk of ambiguity or confusion.
The single tool follows a clear verb_noun pattern, consistent with common conventions.
A single tool for a transit server like TTC is extremely limited; typical servers would include many more tools for routes, schedules, stops, etc.
Only fare information is provided; there are obvious gaps for routes, schedules, real-time updates, and other transit data.