MCP Aruba Email & Calendar Server

Overview Schema Source Related Servers Discussions Admin

list_calendar_events

Retrieve calendar events within a specified date range, with optional start and end dates plus a result limit, to view schedules and plan around upcoming appointments.

Instructions

List calendar events within a date range.

Args: start_date: Start date in ISO format (default: today) end_date: End date in ISO format (default: 30 days from now) limit: Maximum number of events to return (default: 50)

Returns: List of calendar events

Example: list_calendar_events( start_date="2025-12-01T00:00:00", end_date="2025-12-31T23:59:59", limit=20 )

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_calendar_events"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`end_date`	No
`start_date`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Nov 9, 2026

TDQS

B3.3/5.0

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 disclosure burden. It never states that the call is read-only, what calendar or account scope it reads, how recurring or cancelled events are handled, or how timezones are interpreted — all material for a calendar listing tool.

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

Conciseness4/5

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

The one-line purpose is front-loaded, followed by compact Args/Returns sections that are easy to scan. The Example block largely restates the Args section and could be dropped without information loss, so it is slightly padded rather than tight.

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

Completeness3/5

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

The tool is simple (three optional params, output schema present), and the description covers parameter meaning and return type adequately. However, with zero annotation coverage it leaves out behavioral facts an agent would want — read-only nature, calendar scope, and what 'limit' truncation implies (pagination or silent cutoff).

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 0%, so the description must compensate, and it does: it gives ISO format for both dates, a per-parameter default for each, and meaning for limit ('maximum number of events to return'). It even discloses a dynamic default for start_date ('today') that the schema shows only as null, adding genuine value. A worked example reinforces the format.

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

Purpose4/5

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

States a specific verb and resource ('List calendar events') plus the scoping dimension ('within a date range'), which clearly separates it from mutation siblings like create_calendar_event and delete_calendar_event. It does not explicitly name or contrast any sibling, which keeps it short of a 5.

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?

Usage is only implied: the defaults (today through 30 days out) suggest calling with no arguments for an upcoming-events view, and the range arguments suggest narrowing. There is no explicit when-to-use/when-not guidance, no mention of alternatives such as searching emails for invites, and no prerequisites (which calendar, auth) are stated.

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