Skip to main content
Glama

get-specific-calendar-event

Read-only

Retrieve a specific calendar event from a Microsoft 365 calendar by ID, with options to select fields, expand details, and set timezone.

Instructions

The events in the calendar. Navigation property. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectNoComma-separated fields to return, e.g. id,subject,from,receivedDateTime
expandNoExpand related entities
calendarIdYesPath parameter: calendarId
eventIdYesPath parameter: eventId
fetchAllPagesNoFollow @odata.nextLink and merge up to 100 pages into one response. Can return enormous payloads—only when the user explicitly needs a full export. Prefer a small $top first, then paginate or narrow with $filter/$search.
includeHeadersNoInclude response headers (including ETag) in the response metadata
excludeResponseNoExclude the full response body and only return success or failure indication
timezoneNoIANA timezone name (e.g., "America/New_York", "Europe/London", "Asia/Tokyo") for calendar event times. If not specified, times are returned in UTC.
expandExtendedPropertiesNoWhen true, expands singleValueExtendedProperties on each event. Use this to retrieve custom extended properties (e.g., sync metadata) stored on calendar events.
Behavior2/5

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

The description states 'Read-only' which aligns with the readOnlyHint annotation, but adds no additional behavioral context beyond that. It does not mention that the tool returns a single event, any side effects, authentication needs, or other operational traits. The annotation already covers read-only status, so description adds minimal value.

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

Conciseness2/5

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

The description is extremely short (three fragments) but omits critical information. This is under-specification rather than conciseness. The description should be at least a full sentence stating the action and key details.

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

Completeness1/5

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

Despite having 9 parameters and no output schema, the description fails entirely to explain what the tool returns. It simply says 'The events' which is ambiguous and suggests a list, while the tool name indicates a single event. With no output schema, the description must clarify return value structure, but it does not.

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% for all 9 parameters, so baseline is 3. The description provides no additional parameter meaning beyond what the schema already offers. It does not explain how parameters interact or any constraints not in the schema.

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

Purpose2/5

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

The description 'The events in the calendar. Navigation property. Read-only.' is vague and does not clearly state that this tool retrieves a single specific calendar event. It reads more like a metadata note than a functional description. The purpose is partially inferable from the name but the description fails to articulate it.

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 guidance is provided on when to use this tool versus alternatives like 'get-calendar-event' or 'list-calendar-events'. The description lacks any context about preferred usage scenarios or sibling differentiation.

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/Softeria/ms-365-mcp-server'

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