Skip to main content
Glama
Sign In
Outlook MCP

Outlook MCP

by lanSall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

outlook_list_calendar

Retrieve upcoming Outlook calendar events for a specified number of days, with an optional limit on the number of events returned.

Instructions

List upcoming calendar events.

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": "outlook_list_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only says 'List', implying a read-only operation, but does not explain authentication requirements, rate limits, side effects, or the exact scope of 'upcoming'. This lack of detail leaves the agent guessing about the tool's behavior beyond the basic action.

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, concise sentence that states the core function without redundancy. Every word earns its place, and the structure is appropriate for the tool's simplicity.

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?

Despite the tool's simplicity, the description omits critical details: the meaning of the parameters, the format or scope of returned events, and any authentication expectations. With no output schema or parameter explanations, the description is insufficient for an agent to invoke the tool correctly beyond a basic guess.

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

Parameters2/5

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

The input schema defines two parameters (top and days) with defaults and bounds but no descriptions. The tool description does not explain what these parameters control or how they relate to 'upcoming events'. Since schema coverage is 0%, the description fails to compensate for the missing parameter documentation.

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 tool lists upcoming calendar events, using a specific verb and resource. It distinguishes itself from sibling tools like outlook_list_emails and outlook_get_profile, which handle different domains. The word 'upcoming' adds temporal scope, making the purpose unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites (e.g., authentication), and no exclusions. It merely states what the tool does without context on when it is appropriate or how it fits with sibling tools.

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