day-planner-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRANSPORT | No | The transport protocol to use for the server. Set to 'http' to enable connectivity for the web client (defaults to stdio). |
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 | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| load_day_plannerA | Opens an interactive day planning dashboard showing your calendar, emails, and docs. The dashboard shows:
Use this to give the user a holistic view of their day. |
| handle_day_planner_actionA | Processes an interactive action triggered by the user in the Day Planner UI. Action types:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| ui://day-planner/app.html |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one handles specific user actions in the Day Planner UI, while the other loads the entire interactive dashboard. There is no overlap or ambiguity between them, as they serve different functions in the user workflow.
Both tools follow a consistent snake_case naming pattern with clear verb_noun structure: 'handle_day_planner_action' and 'load_day_planner'. The naming is predictable and readable, making it easy for an agent to understand their roles.
With only 2 tools, the server feels too thin for its stated purpose of day planning, which involves calendar events, emails, documents, and interactive actions. A more comprehensive set would be expected to cover operations like creating events, managing tasks, or updating priorities, rather than just handling actions and loading a dashboard.
The tool surface is severely incomplete for day planning. While it covers loading a dashboard and handling some UI actions, it lacks core CRUD operations for managing calendar events, emails, or documents. There are significant gaps that would cause agent failures, such as no ability to create or modify events, send emails, or organize tasks beyond the provided actions.