CommuteHell
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TMAP_API_KEY | Yes | TMAP 대중교통 API 인증 | |
| OPENDATA_API_KEY | Yes | 기상청 및 공휴일 API 인증 |
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 |
|---|---|
| get_commute_difficultyB | 출발지와 도착지 좌표로 퇴근 난이도를 계산합니다. |
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 1 tool
With only one tool, there is no possibility of confusion or misselection. The purpose of get_commute_difficulty is clear and distinct.
The single name follows the snake_case verb_noun pattern (get_commute_difficulty), which is conventional and consistent by default.
The server has only one tool, which is too few for the apparent domain of 'CommuteHell'. A single calculation function feels more like a standalone service than a coherent MCP tool set.
The tool covers the core operation of calculating difficulty but misses auxiliary capabilities such as retrieving traffic details, comparing route options, or explaining contributing factors. This creates notable gaps for a comprehensive commute analysis.