Skip to main content
Glama
OnStartups

Agent.ai MCP Server

by OnStartups

get_calendar_events_list

Retrieve calendar events from Google or Outlook with filters for event timing, count, and calendar scope to organize your schedule.

Instructions

Build a list of the user's calendar events from Google Calendar, Outlook Calendar, or all connected calendars.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
calendar_providerYesCalendar service to use. Select 'All Connected Calendars' to combine events from all providers.all
event_filterYesSelect which events to retrieve based on their timing.future
with_notetaker_transcript_onlyNoWhen Event Filter is Past, only include events that have a notetaker recording with transcript (for post-meeting follow-up agent). Default: off for backwards compatibility.
max_eventsYesMaximum number of events to retrieve (e.g., 30).30
primary_calendar_onlyYesOnly retrieve events from the user's primary calendar.
output_formatYesChoose how the calendar events should be formatted.json
output_variable_nameYesProvide a variable name to store the calendar events list, like 'calendar_events' or 'upcoming_meetings'.
Behavior2/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 only states the action without disclosing read-only nature, performance implications, rate limits, auth requirements, or side effects. For a tool with no annotations, this is insufficient transparency.

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, well-structured sentence that is front-loaded with the action. Every word adds value, with no redundancy.

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 7 parameters and no output schema, the description is too brief. It does not mention return format, ordering, pagination, error handling, or how the multiple filters interact. A more comprehensive description is needed for this complexity.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds minimal value beyond what the schema already provides for each parameter. It does not explain parameter interactions or provide additional context.

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 verb (Build) and resource (list of calendar events), and specifies the supported providers (Google Calendar, Outlook, or all). This distinguishes it from sibling tools like enrich_calendar_event or meeting_prep tools that focus on single events or meeting preparation.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool vs alternatives. There is no mention of prerequisites, context, or when not to use it. Among siblings, many meeting-related tools exist, but no direct comparison or exclusion criteria are provided.

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/OnStartups/agentai-mcp-server'

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