Skip to main content
Glama
seandkendall

productivity-mcp

by seandkendall

get_event

Retrieve a single calendar event with complete details by providing the event ID.

Instructions

Fetch a single calendar event with full detail.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYes
accountNo
calendarNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler for 'get_event'. It is registered with @mcp.tool(), decorated with @_logged, and delegates to the calendar provider's get_event method, then converts the result to a dict.
    @mcp.tool()
    @_logged
    def get_event(
        event_id: str,
        account: str | None = None,
        calendar: str | None = None,
    ) -> dict[str, Any]:
        """Fetch a single calendar event with full detail."""
        return _calendar(account).get_event(calendar, event_id).to_dict()
  • Abstract method definition for get_event in CalendarProvider base class. Defines the interface: takes calendar (str|None) and event_id (str), returns a CalendarEvent.
    @abstractmethod
    def get_event(self, calendar: str | None, event_id: str) -> CalendarEvent: ...
  • Tool registration via @mcp.tool() decorator on the get_event function in server.py. This is how the tool is registered with the MCP framework.
    @mcp.tool()
    @_logged
    def get_event(
        event_id: str,
        account: str | None = None,
        calendar: str | None = None,
    ) -> dict[str, Any]:
        """Fetch a single calendar event with full detail."""
        return _calendar(account).get_event(calendar, event_id).to_dict()
  • Google Calendar implementation of get_event. Calls the Google Calendar API events().get() and converts the raw result to a CalendarEvent.
    def get_event(self, calendar: str | None, event_id: str) -> CalendarEvent:
        cal_id = self._resolve_calendar(calendar)
        raw = self._svc().events().get(calendarId=cal_id, eventId=event_id).execute()
        return self._to_event(raw, cal_id)
  • CalDAV implementation of get_event. Iterates over calendar events, parses iCal data, and finds the event by ID.
    def get_event(self, calendar: str | None, event_id: str) -> CalendarEvent:
        cal = self._find_calendar(calendar)
        for item in cal.events():
            for ev in _parse_ical(item.data, cal.name):
                if ev.id == event_id:
                    return ev
        raise KeyError(f"Event {event_id} not found in calendar {cal.name}")
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 burden. It states 'full detail' hinting at rich output, but does not disclose any behavioral traits such as read-only nature, rate limits, or authentication needs. The description is adequate but minimal.

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

Conciseness5/5

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

The description is a single sentence that directly states the tool's purpose with no extraneous words. It is efficiently front-loaded and every word earns its place.

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?

Given the tool has 0% schema description coverage and no annotations, the description should compensate with parameter semantics and usage guidance. While purpose is clear, the lack of parameter detail and usage context makes it incomplete for an agent to reliably invoke without additional inference.

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?

The input schema has 0% description coverage, yet the description provides no explanation of parameters (event_id, account, calendar). It does not clarify that event_id is required or the purpose of optional account/calendar parameters, leaving the agent to infer from names alone.

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 uses the verb 'Fetch' with resource 'single calendar event' and qualifier 'full detail', clearly distinguishing from sibling tools like list_events (multiple events) and search_events (query-based). It unambiguously identifies what the tool does.

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 the tool is for retrieving a specific event with full detail, but does not explicitly state when to use it versus alternatives like list_events or search_events. No exclusion criteria or prerequisite context is given.

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/seandkendall/productivity-mcp'

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