Skip to main content
Glama
Office MCP Server

Office MCP Server

by hvkshetry

notifications

Create, list, renew, or delete webhook subscriptions that send Microsoft 365 change events to a specified URL.

Instructions

Manage webhook subscriptions for change notifications: create, list, renew, or delete

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": {
      "operation": "<operation>"
    },
    "name": "notifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourceNoThe resource to subscribe to changes for (for create)
operationYesThe operation to perform
changeTypeNoThe type of changes: created, updated, deleted (for create)
subscriptionIdNoSubscription ID (for renew/delete)
notificationUrlNoThe URL where notifications should be sent (for create)
expirationMinutesNoMinutes until subscription expires (default: 60, max: 4230)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden and mostly does not meet it. It does not say whether delete is irreversible, whether renew extends or replaces a subscription, what happens to an existing subscription for the same resource/changeType, or anything about delivery retries or auth requirements — all critical for a tool that includes a destructive 'delete' path.

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 front-loaded sentence with the resource first and the operation set second; no filler and nothing to trim.

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?

For a 6-parameter, multi-operation tool that includes deletion and has no annotations and no output schema, the description is too thin. It should at minimum flag the destructive path and the subscription lifecycle implications, which matter more here than parameter details the schema already handles.

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 description coverage is 100%, and each parameter already states which operation it applies to ('for create', 'for renew/delete') and gives the expiration default and max. The description only restates the operation list, adding no meaning beyond the schema, so the baseline 3 for high coverage applies.

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 resource (webhook subscriptions for change notifications) and enumerates the concrete operations (create, list, renew, delete), so an agent knows exactly what domain this covers. It does not need sibling differentiation because no sibling tool in the catalog overlaps with notifications.

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?

The four operations imply what the tool can do, but there is no explicit guidance on when to reach for it versus an alternative, nor any statement of prerequisites such as required permissions or an existing subscription needed for renew/delete. Usage is inferable rather than stated.

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