Skip to main content
Glama
giantrotta24

google-mcp

by giantrotta24

calendar_events_work

Retrieve events from configured work calendars within a specified time range, with optional limit on results.

Instructions

List events for the configured work account calendars.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
time_minYes
time_maxYes
max_resultsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • tools.py:57-69 (handler)
    The MCP tool handler function `calendar_events_work`. It loads work account credentials and delegates to the `calendar_events` API function with optional calendar name filters.
    @mcp.tool()
    def calendar_events_work(time_min: str, time_max: str, max_results: int = 50) -> dict[str, Any]:
        """List events for the configured work account calendars."""
        result = _load_or_error("work")
        if isinstance(result, dict):
            return result
        return calendar_events(
            result,
            time_min,
            time_max,
            max_results,
            calendar_names=_work_calendar_filters(),
        )
  • api.py:98-103 (schema)
    The `calendar_events` API function that this tool delegates to. It accepts credentials, time range, max results, and optional calendar name filters, queries the Google Calendar API, and returns structured event data.
    def calendar_events(
        creds: Credentials,
        time_min: str,
        time_max: str,
        max_results: int = 50,
        calendar_names: list[str] | None = None,
  • tools.py:57-58 (registration)
    The `@mcp.tool()` decorator registers `calendar_events_work` as an MCP tool with the FastMCP server instance.
    @mcp.tool()
    def calendar_events_work(time_min: str, time_max: str, max_results: int = 50) -> dict[str, Any]:
  • The `_work_calendar_filters()` helper reads the `GOOGLE_MCP_WORK_CALENDAR` env var to optionally filter work calendars by name/ID.
    def _work_calendar_filters() -> list[str] | None:
        """Return optional work calendar filter from env."""
        raw = os.getenv(WORK_CALENDAR_FILTER_ENV, "").strip()
        return [raw] if raw else None
  • The `WORK_CALENDAR_FILTER_ENV` constant defining the environment variable name `GOOGLE_MCP_WORK_CALENDAR`.
    WORK_CALENDAR_FILTER_ENV = "GOOGLE_MCP_WORK_CALENDAR"
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as authentication needs, rate limits, pagination, or error handling. It only states 'List events', leaving significant gaps.

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

Conciseness3/5

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

The description is very concise (one sentence), which is good for brevity, but it sacrifices essential information, making it less effective.

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

Completeness2/5

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

Even though an output schema exists (per context), the description lacks details about parameters and behavioral context, leaving the agent underinformed for a tool with no annotations.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no meaning to parameters like time_min, time_max, or max_results. It fails to explain expected formats or constraints.

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

Purpose5/5

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

The description clearly states the action ('List events'), the resource ('events'), and the scope ('configured work account calendars'), effectively distinguishing it from sibling 'calendar_events_personal'.

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?

The description implies usage for work account calendars but provides no explicit guidance on when to use this tool versus alternatives (e.g., calendar_events_personal) or when-not-to-use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/giantrotta24/multi-account-google-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server