Weekly Planning Assistant MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_OAUTH_CREDENTIALS | Yes | Path to the Google OAuth credentials JSON file |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_weekA | Get a comprehensive overview of the upcoming week. |
| find_danger_zonesA | Identify scheduling problems and conflicts. |
| suggest_workout_slotsA | Find optimal times for booking fitness classes. |
| check_commute_requirementsA | Identify which days require office commute. |
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 4 tools
Each tool has a clearly distinct purpose: weekly overview, problem detection, workout scheduling, and commute detection. Overlap is minimal (check_commute_requirements focuses on office days, while analyze_week includes office days as part of a broader analysis, but descriptions clearly differentiate).
All tool names follow a consistent verb_noun pattern: analyze_week, find_danger_zones, suggest_workout_slots, check_commute_requirements. No deviations in style or casing.
Four tools are well-scoped for a weekly planning assistant, covering analysis, conflict detection, scheduling suggestions, and commute needs. Each tool earns its place without redundancy.
The surface covers key planning tasks: analysis, conflict detection, workout suggestions, and commute checks. However, it lacks tools for modifying the calendar (e.g., creating events) or deeper integration like travel time estimation, which could be minor gaps for a planning assistant.