Skip to main content
Glama
Softeria

Microsoft 365 MCP Server

by Softeria
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

delete-focused-inbox-override

delete-focused-inbox-override
Destructive

Delete a Focused Inbox override by ID so future messages from that sender revert to the default classifier behavior. List overrides first to get the ID.

Instructions

Delete an override specified by its ID.

šŸ’” TIP: Deletes a Focused Inbox override. Future messages from that sender revert to the Outlook ML classifier's default behavior. Use list-focused-inbox-overrides to find the ID first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoFor destructive operations when the confirm gate is enabled (MS365_MCP_REQUIRE_CONFIRM=true; off by default). Set to true only after the user has explicitly approved this action. When the gate is on, calls without confirm: true return { error: "confirmation_required" } without touching user data.
If-MatchNoETag
includeHeadersNoInclude response headers (including ETag) in the response metadata
excludeResponseNoExclude the full response body and only return success or failure indication
inferenceClassificationOverrideIdYesValue for the 'inferenceClassificationOverrideId' path segment. Pass it under the name 'inferenceClassificationOverrideId', not as 'id'. Use the 'id' field of the inference classification override object as returned by Microsoft Graph.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.134.4
  2. Removedv0.131.2
  3. Changed1 schema field changedv0.131.1
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "For destructive operations when the confirm gate is enabled (MS365_MCP_REQUIRE_CONFIRM=true; off by default). Set to true only after the user has explicitly approved this action. When the gate is on, calls without confirm: true return { error: \"confirmation_required\" } without touching user data.",
+  "type": "boolean"
+}
  4. Addedv0.114.0
  5. Removedv0.112.2
  6. Addedv0.110.0
  7. Removedv0.108.0
  8. Addedv0.96.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description doesn't need to restate that. It adds value by disclosing the behavioral consequence: 'Future messages from that sender revert to the Outlook ML classifier's default behavior.' This goes beyond the bare 'delete' and gives the agent a clear understanding of the side effect. However, it doesn't mention irreversibility (covered by destructiveHint) or any authorization requirements, which are reasonable to omit given the annotations.

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 two sentences: a direct statement of the action and a concise tip. The primary verb is front-loaded, and the tip is actionable without extra fluff. There is zero waste; every sentence serves a purpose for correct invocation.

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 destructive operation with one required parameter, the description covers the core behavior, the consequence, and how to obtain the required ID. The sibling set includes list and update versions, so the tool's role is clear. An output schema is absent, so no return format is specified, but that's not unusual for a delete operation. The description is complete enough for an agent to call it correctly given the schema and annotations.

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%, so all parameters are documented in the schema itself. The description does not add extra semantic meaning beyond what the schema provides (e.g., it doesn't elaborate on the confirm parameter's behavior or If-Match usage). It only points to list-focused-inbox-overrides for finding the ID, which is a usage hint rather than parameter semantics. The baseline of 3 is appropriate since the schema fully covers parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Delete') and resource ('an override'), and further clarifies it's a Focused Inbox override. The tip explicitly mentions the behavior change (reverting to default sentiment) and distinguishes it from list/create/update siblings. An agent can clearly tell what this tool does.

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?

The description provides a direct usage hint: 'Use list-focused-inbox-overrides to find the ID first.' This is a concrete prerequisite for calling the tool correctly. It doesn't explicitly state when not to use it, but the destructive nature and the alternative (update) are implied. The guidance is adequate for correct invocation, though it could be more explicit about scenarios where deletion might be inappropriate.

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