Weekly Planning Assistant MCP

Overview Schema Source Related Servers Discussions Admin

analyze_week

Get a weekly calendar analysis showing office days, meeting hours, gaps, and back-to-back blocks per day. Plan your schedule with clear breakdowns and summary stats.

Instructions

Get a comprehensive overview of the upcoming week.

Analyzes calendar events to provide day-by-day breakdown with office days,
meeting hours, gaps, and back-to-back meeting blocks.

Args:
    start_date: Week start date (YYYY-MM-DD). Defaults to next Monday.
    calendar_ids: List of calendar IDs to analyze. Defaults to ["primary"].

Returns:
    Complete weekly analysis with per-day breakdowns and summary statistics.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`start_date`	No
`calendar_ids`	No

Output Schema

TableJSON Schema

Name	Required	Description
`days`	Yes	Per-day breakdown
`end_date`	Yes	Week end date (YYYY-MM-DD)
`start_date`	Yes	Week start date (YYYY-MM-DD)
`busiest_day`	Yes	Day with most meeting hours
`lightest_day`	Yes	Day with least meeting hours
`office_day_count`	Yes	Number of office days
`total_scheduled_hours`	Yes	Total meeting hours for the week

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden. It discloses the analysis dimensions and return scope, but says nothing about permissions, whether it falls back gracefully when calendars are empty, or any rate/volume constraints. For a read-only analysis tool this is adequate but leaves gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with a one-line summary, then structured Args/Returns sections with no filler. Every sentence carries information; the only minor redundancy is restating return contents given a dedicated output schema exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't detail return shapes, yet it summarizes them helpfully. The two optional parameters are fully covered, and the read-only analysis nature is clear; missing only explicit guidance on when to prefer it over siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: it documents both parameters with their expected format (YYYY-MM-DD), their defaults (next Monday, ['primary']), and their meaning. This meaningfully exceeds the bare schema, though it adds no validation or edge-case notes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('analyze' + 'week' of calendar events) and enumerates the concrete outputs: day-by-day breakdown, office days, meeting hours, gaps, back-to-back blocks. It is clearly distinct from the sibling tools (danger zones, workout slots, commute), though it never explicitly names or contrasts them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'upcoming week' and the default of next Monday, giving an agent a sense of the intended scope. However, there is no explicit when-to-use, when-not-to-use, or comparison to any alternative tool, so the agent must infer the trigger conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server