Cafeteria MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CAFETERIA_SEQ | Yes | Cafeteria sequence. | |
| CAFETERIA_CAMPUS | Yes | Campus code. | |
| CAFETERIA_ORIGIN | No | Optional origin header; defaults to derived from CAFETERIA_API_URL. | |
| CAFETERIA_API_URL | Yes | Form-post API URL for cafeteria menu lookup. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_cafeteria_menuA | 환경변수로 설정된 식당 API에서 메뉴를 조회합니다. |
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
The server has only one tool, so there is no ambiguity or risk of confusing it with others. Its purpose is clearly described as retrieving the cafeteria menu.
The single tool name follows a clear verb_noun pattern (get_cafeteria_menu), which is standard and unambiguous. With only one tool, there is no inconsistency.
The server has only one tool, which feels thin and borderline for a general-purpose server. However, it may be acceptable for a narrowly-scoped cafeteria menu fetcher, though it limits broader utility.
The tool covers the core use case of retrieving the cafeteria menu. However, it lacks any parameters for specifying a date or restaurant, and there is no backup or additional features, making it somewhat limited but not severely incomplete.