Skip to main content
Glama

Outlook List Calendar

outlook_list_calendar
Read-only

List upcoming Outlook calendar events from now up to 31 days ahead, so you can check your schedule before planning meetings or replying with availability.

Instructions

List calendar events starting from now, up to 31 days ahead.

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
daysNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds a useful behavioral detail — the window begins at the current time rather than the start of the day — but says nothing about result ordering, volume, or what happens when the window is exhausted.

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?

A single sentence with the scope constraint front-loaded and no filler. Nothing could be removed without losing information.

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?

An output schema exists, so return values needn't be explained. However, for a one-parameter tool with zero schema coverage, the description leaves the only parameter undocumented and its interaction with the stated 31-day ceiling unresolved.

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?

Schema description coverage is 0% for the single parameter, so the description must carry the meaning of 'days'. It never mentions 'days' or its default of 7, and its hard 'up to 31 days ahead' framing leaves unclear whether the parameter can override or is capped by that limit.

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?

The description names a specific verb and resource (list calendar events) plus a time scope (from now, up to 31 days ahead), which clearly separates it from siblings like outlook_create_event or outlook_read_mail. It does not explicitly name a sibling to contrast with, but the read/list framing 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 Guidelines3/5

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

Usage is implied by the time scoping ('starting from now'), so an agent can infer this is a forward-looking agenda listing. There is no explicit statement of when to prefer this over outlook_list_tasks or outlook_search_mail, and no exclusions or prerequisites.

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