MCP Canteen Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CANTEEN_API_BASE | Yes | API base URL (provided by system administrator) | |
| CANTEEN_API_TOKEN | Yes | API authentication token (obtain from system administrator) |
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_canteen_dataC | 获取餐厅就餐人数数据 |
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 ambiguity or overlap between tools. The single tool 'get_canteen_data' has a clear, distinct purpose of retrieving canteen occupancy data.
The naming follows a consistent verb_noun pattern with 'get_canteen_data'. Since there is only one tool, it inherently maintains perfect consistency without any deviations or mixed conventions.
A single tool is too few for a server named 'MCP Canteen Server', which suggests a broader scope for managing canteen-related data. This minimal toolset likely leaves significant functionality gaps, such as updating or analyzing data, making it feel incomplete for the domain.
The toolset is severely incomplete for a canteen management domain. It only provides data retrieval ('get_canteen_data'), with no tools for creating, updating, or deleting data, or for other operations like menu management or reservation handling, leading to dead ends for agents.