Skip to main content
Glama
anastasiakrause

Weekly Planning Assistant MCP

check_commute_requirements

Analyze calendar events to identify office commute days and report earliest required office times, plus warnings for early morning commitments.

Instructions

Identify which days require office commute.

Analyzes calendar events to detect office days and provides:
- Which days require office presence
- Earliest time needed at office
- Warnings about early morning commitments

Args:
    start_date: Start date (YYYY-MM-DD)
    end_date: End date (YYYY-MM-DD)
    office_indicators: Keywords indicating office presence. Defaults to config.
    calendar_ids: List of calendar IDs. Defaults to ["primary"].

Returns:
    List of office days with commute information and warnings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_dateYes
start_dateYes
calendar_idsNo
office_indicatorsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/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 key outputs (office days, earliest time, early morning warnings) and that it analyzes calendar events, but omits permission needs, rate limits, and any caveats about detection reliability.

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?

The description is well-structured with a front-loaded summary, a bulleted list of provided information, and clear Args/Returns sections. It is slightly verbose in the bullet list but remains efficient and every part earns its place.

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?

Given the complexity (calendar analysis, 4 parameters) and the presence of an output schema, the description is quite complete. It explains what the tool does, what inputs mean, and what the returns contain, though it could mention any prerequisite calendar access permissions.

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. It does so by documenting all four parameters with expected formats, defaults, and meaning (e.g., 'YYYY-MM-DD' for dates, 'Defaults to config' for office_indicators). Only minor details like timezone handling are missing.

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 (identify) and resource (days requiring office commute), and describes its analysis approach (analyzes calendar events to detect office days). It doesn't explicitly differentiate from siblings, which operate on different domains, but the purpose is crystal clear.

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 context is implied by the description of the analysis and its output, but there is no explicit when-to-use, when-not-to-use, or alternative tool guidance (e.g., versus analyze_week). The agent can infer it's for commute planning, but no routing is provided.

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