Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

Cancel an Outlook event

m365_calendar_cancel
Destructive

Cancel an event the mailbox organizes and tell its attendees, with an optional note. On accounts with an owner it waits for the owner's approval by default. $0.001. Costs $0.001 per call; nothing if it fails.

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": {
      "event_id": "<event_id>"
    },
    "name": "m365_calendar_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentNo
mailboxNoOne of the mailboxes the agent may act as; optional when only one is connected.
event_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Adds meaningful behavior beyond annotations: attendees are told, an optional note can be included, owner approval may be required, and the call costs $0.001 unless it fails. With destructiveHint already set, this covers side effects well, though permanence or undo behavior is not described.

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?

Front-loads the purpose in a compact sentence, then adds approval and cost details. The cost statement is slightly redundant ('$0.001. Costs $0.001 per call...'), but the overall length is appropriate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple destructive mutation with no output schema, the description supplies important side-effect, approval, and cost context. It leaves event_id semantics and exact approval workflow details implicit, but is largely complete for selection and 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?

Schema coverage is only 33%; the description clarifies comment as an optional note to attendees and refers to the mailbox context. However, the required event_id parameter is not explained beyond implying that it identifies the event.

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?

States a specific verb ('Cancel') and resource ('an event the mailbox organizes'), and the title identifies Outlook. It does not name sibling tools, but the scope is clear enough to distinguish it from creating or listing events.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explains the applicable context: events the mailbox organizes, with owner approval on some accounts. It stops short of naming alternatives or explicit when-not-to-use cases.

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

All Conecto toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources