internal-calendar-scoping

Resolve unbounded calendar queries with time-bounded ListCalendarView and FindMeetingTimes patterns.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/JinLee794/L.C.G --skill internal-calendar-scoping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: internal-calendar-scoping
Source: https://github.com/JinLee794/L.C.G/tree/main/.github/skills/internal-calendar-scoping
Command: npx skills add https://github.com/JinLee794/L.C.G --skill internal-calendar-scoping

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Calendar MCP query scoping: efficient event retrieval, meeting time discovery, room booking, and scheduling patterns for the native Calendar MCP server. Prevents unbounded event listing and unnecessary API calls. Triggers: calendar search, find meeting, list events, schedule meeting, book room, find meeting time, calendar view, today meetings, upcoming meetings, Calendar MCP, create event. DO NOT USE FOR: cross-medium day triage combining mail + calendar + Teams (use m365-search daily triage).

Core Features & Use Cases

  • Provides time-bounded retrieval patterns to avoid unbounded queries.
  • Distinguishes between read (ListCalendarView) and write (CreateEvent, etc.) MCP tools to prevent unsafe operations.
  • Guides room booking and scheduling flows for calendar-centric workflows.

Quick Start

Use ListCalendarView with a time-bounded window to retrieve events, then FindMeetingTimes to propose slots before creating an event.

Frequently Asked Questions about internal-calendar-scoping

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent unbounded calendar queries when retrieving upcoming meetings using MCP tools?

Use FindMeetingTimes to propose available time slots before creating an event. This separates read operations from write operations, ensuring you query availability first and only use CreateEvent once a suitable meeting time is confirmed.

What is the correct way to separate read and write operations in Calendar MCP workflows?

For room booking and scheduling, use ListCalendarView to retrieve time-bounded events, then apply FindMeetingTimes to discover available slots. This pattern ensures efficient calendar-centric workflows without triggering unbounded event listing or unnecessary API calls.

Can I use this approach for cross-medium daily triage combining mail, calendar, and Teams?

No, you should not use this approach for cross-medium daily triage combining mail, calendar, and Teams. This specifically targets calendar-centric scheduling workflows, requiring a different tool for broader multi-medium daily triage.

When do I need time-bounded patterns for calendar event retrieval?

You need time-bounded patterns for calendar event retrieval whenever querying upcoming meetings, finding available times, or booking rooms. These patterns enforce safe query limits on ListCalendarView calls, preventing unbounded data fetching from the Calendar MCP server.