Adam OS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_business_overviewA | Get a complete overview of both restaurants — Reading Club and Seneca Trattoria — including current KPIs, alerts, and data status. |
| get_labor_summaryA | Get labor hours, cost, and labor percentage. Works with real Toast data if imported, otherwise shows current known metrics. |
| get_employee_hoursB | Get hours and pay for employees. Flags overtime. Use to check if anyone is approaching overtime threshold. |
| get_sales_summaryC | Get sales, covers, and average check data from imported Toast reports. |
| get_server_salesC | Get per-server sales, covers, and tips. Used for tip pool calculations. |
| calculate_tip_poolC | Calculate tip pool distribution based on imported server sales data. |
| import_toast_csvA | Import a Toast POS CSV export. Auto-scans ~/Desktop/Toast Imports folder if no path given. Accepts labor, sales summary, or server sales reports. |
| list_importsA | List all previously imported Toast CSV files. |
| get_tasksB | Get tasks and to-dos. Filter by priority or status. |
| add_taskC | Add a new task or action item. |
| complete_taskC | Mark a task as complete. |
| save_noteC | Save a shift note, incident report, or any observation. |
| get_notesC | Get saved shift notes, incidents, or observations. |
| system_diagnosticB | Run a complete health check of Adam OS. Check all data, tools, and status. |
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 14 tools
Each tool targets a distinct aspect of restaurant management: tasks, sales, labor, notes, imports, and system diagnostics. There is no overlap; even related tools like get_sales_summary and get_server_sales are clearly differentiated by scope.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., add_task, get_sales_summary, import_toast_csv). No mixing of conventions or vague verbs.
With 14 tools covering tasks, sales, labor, imports, and health checks, the count is well-scoped for a restaurant management assistant. Each tool feels necessary without redundancy.
The tool set covers core CRUD operations for tasks and notes, plus detailed reporting and imports. Minor gaps exist—no update or delete for tasks/notes—but the core workflows are complete, and the system_diagnostic tool provides additional oversight.