Skip to main content
Glama
Sign In
fulcradynamics

Fulcra MCP Server

by fulcradynamics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get Calendar Events

get_calendar_events
Read-only

Retrieve calendar events for a specified time range, or list calendars grouped by account/source. Use it to see event participants and responses when include_participants is enabled.

Instructions

Get the user's calendar events in a time range, or, without a range, list their calendars grouped by account/source.

Each carries a participant_count; pass include_participants=true when you need who was invited and their responses.

Input Schema

NameRequiredDescriptionDefault
end_timeNoRange end (exclusive). Must include tz (ISO8601).
calendarsNoEvents only: just these calendars (names or IDs); default is all.
start_timeNoRange start (inclusive). Must include tz (ISO8601).
fulcra_useridNoRetrieve calendars or events of another Fulcra user (if shared)
include_participantsNoEvents only: include each event's participant list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv1.18.7
    • removedInput schema / properties / calendars / anyOf
      Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / calendars / default
      Removed value: -null
    • changedInput schema / properties / calendars / description
      Previous value: -"Only these calendars (names or IDs); default is all."New value: +"Events only: just these calendars (names or IDs); default is all."
    • addedInput schema / properties / calendars / items
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / calendars / type
      Added value: +"array"
    • removedInput schema / properties / fulcra_userid / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / fulcra_userid / default
      Removed value: -null
    • changedInput schema / properties / fulcra_userid / description
      Previous value: -"Retrieve events of another Fulcra user (if shared)"New value: +"Retrieve calendars or events of another Fulcra user (if shared)"
    • addedInput schema / properties / fulcra_userid / type
      Added value: +"string"
    • changedInput schema / properties / include_participants / description
      Previous value: -"Include each event's participant list."New value: +"Events only: include each event's participant list."
    • removedInput schema / required
      Removed value: -[
-  "start_time",
-  "end_time"
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. Addedv1.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, non-destructive operation, so the description does not need to restate safety. It adds useful behavioral detail beyond the annotations: the no-range mode returns calendars grouped by account/source, and events expose participant_count unless include_participants is requested. Pagination, limits, and auth behavior are not covered, preventing a 5.

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 two efficient sentences with the primary behavior front-loaded. Every sentence contributes: the first establishes the two modes, and the second adds participant-related guidance.

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?

For a five-parameter read-only tool with full schema coverage and no output schema, the description covers the key calling modes and participant behavior. It is nearly complete, though additional return-shape or pagination context could help since no output schema exists.

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 coverage is 100%, so the schema already documents all five parameters and sets a baseline of 3. The description adds semantic value by explaining the mode switch around start/end time and clarifying that include_participants=true is for retrieving who was invited and their responses, going slightly beyond the schema text.

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 states a specific verb and resource ('Get the user's calendar events') and clearly defines two modes: event lookup with a time range, or calendar listing without one. There is no direct sibling calendar tool to confuse it with, so the purpose is unambiguous.

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

Usage Guidelines4/5

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

It clearly explains how to choose between the two operational modes: supply a time range for events, omit it to list calendars grouped by source. It also gives an explicit condition for include_participants=true. It stops short of naming exclusions or alternatives, but no sibling calendar tool exists.

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

Deploy Server

Other Tools