Skip to main content
Glama
Sign In
Outlook Assistant

Outlook Assistant

by titanzero
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create-event

Schedule new Outlook calendar events with subject, time, and optional attendees using Microsoft Graph API integration.

Instructions

Creates a new calendar event

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": "<start>",
      "end": "<end>"
    },
    "name": "create-event"
  }
}

Input Schema

NameRequiredDescriptionDefault
subjectYesThe subject of the event
startYesThe start time of the event in ISO 8601 format
endYesThe end time of the event in ISO 8601 format
attendeesNoList of attendee email addresses
bodyNoOptional body content for the event

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 behavioral disclosure. It states 'creates' which implies a write operation, but doesn't disclose any behavioral traits such as permissions required, whether it sends invitations to attendees, error handling, or rate limits. This leaves significant gaps for a mutation tool with no annotation coverage.

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, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse. Every part of the sentence earns its place by conveying essential purpose without redundancy.

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?

Given this is a mutation tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like side effects (e.g., notifications to attendees), error cases, or return values, leaving the agent with insufficient context for reliable invocation.

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?

The schema description coverage is 100%, with all parameters well-documented in the schema (e.g., subject, start/end times in ISO 8601, attendees as email list). The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without compensating value.

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 clearly states the action ('creates') and resource ('new calendar event'), making the purpose immediately understandable. It distinguishes from siblings like 'list-events' or 'cancel-event' by focusing on creation. However, it doesn't specify what distinguishes it from similar creation tools like 'create-folder' or 'create-rule' beyond the resource type.

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. It doesn't mention prerequisites (e.g., authentication status), when not to use it (e.g., for updating events), or direct alternatives among siblings (e.g., 'edit-rule-sequence' for modifications). The agent must infer usage from context alone.

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