Skip to main content
Glama

Outlook Create Event

outlook_create_event

Create an Outlook calendar appointment from a subject and ISO-8601 start and end times, with optional location and body, to schedule meetings directly in your signed-in desktop profile.

Instructions

Create a calendar appointment. Times are ISO-8601, local if they have no offset.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "subject": "<subject>",
      "start_iso": "<start_iso>",
      "end_iso": "<end_iso>"
    },
    "name": "outlook_create_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
confirmNoMust be true to run this write or destructive tool.
end_isoYes
subjectYes
locationNo
start_isoYes

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=false and destructiveHint=false, so the write nature is known. The description adds the meaningful behavioral detail that times are interpreted as local when no offset is supplied, but it omits what the write affects (which calendar/account), whether attendees are notified, and duplicate handling for a create operation.

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?

Two short sentences with zero filler, and the core action is front-loaded ahead of the time-format clarification. Nothing is repeated from the schema.

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 need not be explained, but for a six-parameter write tool the description leaves the calendar target, attendee behavior, and most parameter meanings unaddressed. It is minimally sufficient for a simple event creation call and no more.

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 coverage is only 17% (only 'confirm' is documented), so the description should compensate more than it does. It does add important meaning for start_iso/end_iso by explaining ISO-8601 and offset/local-time interpretation, but subject, body, and location receive no explanation in either place.

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?

"Create a calendar appointment" gives a specific verb and resource, so the agent knows exactly what is produced. It does not distinguish itself from related calendar operations (e.g. listing or drafting), but the action is unambiguous on its own.

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 on when to create an event versus using another path, no prerequisites, and no mention that the tool writes to a user's calendar. The only contextual statement is about time formatting, which is a parameter note rather than usage guidance.

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