IIITH Mess MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MESS_API_KEY | Yes | Your API key from the Mess Portal (get from mess.iiit.ac.in under Settings → API Keys) | |
| MESS_API_URL | No | The URL of the Mess API | https://mess.iiit.ac.in/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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_user_infoB | Get your profile information including name, email, roll number, and last login |
| reset_qr_tokenB | Reset your QR code token used for meal verification at the mess |
| get_mess_infoB | List all available messes with their status (open/closed) |
| get_menuB | Get the menu for all messes on a specific date |
| get_meal_ratesC | Get meal rates for all messes |
| get_meal_capacitiesC | Get available capacity at each mess for a meal |
| get_meal_timingsB | Get meal serving times at each mess |
| get_registrationsB | Get all your meal registrations in a date range (max 2 months) |
| get_registrationC | Get your registration for a specific meal on a date |
| register_mealC | Register for a meal at a specific mess |
| cancel_mealC | Cancel a meal registration |
| uncancel_mealB | Uncancel a previously cancelled meal registration |
| skip_mealC | Mark a meal as skipped (you will still be charged) |
| get_cancellation_countC | Get how many cancellations you've used this month |
| get_billC | Get your mess bill for a month |
| submit_feedbackC | Submit anonymous feedback for a meal you've availed |
| get_meal_ratingB | Get average ratings for a meal |
| get_extrasB | List available extra items for a meal |
| get_extra_registrationsC | Get your registered extra items |
| register_extraC | Register for an extra item |
| delete_extra_registrationC | Delete an extra item registration |
| get_monthly_registrationC | Get your monthly registration for a mess |
| create_monthly_registrationC | Register at a mess for an entire month |
| delete_monthly_registrationC | Delete a monthly registration |
| get_preferencesB | Get your notification and meal preferences |
| update_preferencesC | Update your preferences |
| get_registration_windowB | Get how far in advance you can register for meals |
| get_cancellation_windowB | Get how late you can cancel a meal |
| get_max_cancellationsC | Get the maximum allowed cancellations per month for a meal |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| User Profile | Your mess portal profile information |
| Today's Registrations | Your meal registrations for today |
| This Week's Registrations | Your meal registrations for this week |
| Today's Menu | Menu at all messes for today |
| Current Month's Bill | Your mess bill for the current month |
TDQS
Scored across 29 tools
Each tool has a clearly distinct purpose with no ambiguity; for example, cancel_meal vs. uncancel_meal, get_registration vs. get_registrations, and register_meal vs. create_monthly_registration are well-differentiated. The descriptions specify unique actions on specific resources, preventing misselection.
All tool names follow a consistent verb_noun pattern using snake_case, such as cancel_meal, get_bill, and update_preferences. There are no deviations in naming conventions, making the set predictable and readable.
With 29 tools, the count is too high for the apparent scope of a mess management system, making it feel heavy and potentially overwhelming. A more focused set of 15-20 tools would better suit the domain without sacrificing functionality.
The tool surface provides complete CRUD/lifecycle coverage for mess operations, including registration, cancellation, billing, preferences, and feedback. There are no obvious gaps, and agents can handle all core workflows without dead ends.