Skip to main content
Glama
NJP6969

IIITH Mess MCP Server

by NJP6969

Related Servers

Alternatives to IIITH Mess MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with the IIIT-H mess dining and marketplace systems through resources, tools, and prompts for meal planning, billing analysis, and registration modifications.
      27
      GPL 3.0
    • A
      license
      A
      quality
      D
      maintenance
      Enables LLMs to interact with the IIIT Hyderabad Mess System to manage meal registrations, view menus, and track billing. It supports conversational commands for tasks like cancelling meals, estimating nutrition, and checking account balances.
      45
      5
      AGPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time access to menus from all six MIT Bon Appétit dining halls. It enables users to query daily or weekly schedules and filter options by specific dietary requirements such as vegan, halal, or gluten-free.
      38 npm
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to interact with the Paxaver school lunch platform, allowing users to check menus, order lunch, manage wallet funds, register for events, donate, and perform administrative tasks like managing restaurants and menu items.
      1
      26
      286 npm
      Apache 2.0

    TDQS

    B3.2/5.0

    Scored across 29 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count2/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues