Skip to main content
Glama

outlook_create_event

Create events in Microsoft Outlook calendar without leaving your workflow. Set date, time, and participants directly.

Instructions

Create Outlook calendar event

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:50-50 (registration)
    Tool registration entry in the TOOLS array mapping the name "outlook_create_event" to its description "Create Outlook calendar event"
    ["outlook_create_event", "Create Outlook calendar event"],
  • Handler registration loop that registers all TOOLS including outlook_create_event. This is a stub handler that returns an inspection message. The real implementation is in a native binary.
    for (const [name, desc] of TOOLS) {
      server.tool(name, desc, {}, async () => ({
        content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
      }));
  • Empty schema object '{}' passed for tool input validation parameters, meaning the stub has no defined input schema.
    server.tool(name, desc, {}, async () => ({
Behavior2/5

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

With no annotations, the description fails to disclose any behavioral traits such as permissions needed, side effects, or required preconditions. The single statement offers minimal insight.

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

Conciseness4/5

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

The description is a single concise sentence, but it is so brief that it may be under-specifying. It avoids fluff but lacks necessary context.

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?

The tool has no parameters and no output schema, yet the description does not clarify how the event is created or what the response contains. Critical details like event attributes or success confirmation are omitted.

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?

Input schema has zero parameters with 100% coverage, so baseline is 3. The description adds no parameter information, which is acceptable but does not explain how event details are supplied (e.g., via context).

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 it creates an Outlook calendar event, distinguishing it from generic calendar tools. However, it does not elaborate on the scope or specific Outlook features.

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 'create_calendar_event' or 'outlook_list_events'. Context for appropriate use is missing.

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/lanchuske/local-mcp-releases'

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