Local MCP

Disconnect Microsoft 365 Account

disconnect_m365_account

Destructive

Disconnects ONE Microsoft 365 account and removes its stored sign-in. Pass account (its email, id or display name); with only one account connected it can be omitted, with several it must be given. If it was the default account, the oldest remaining one becomes the default and the answer says which. Reconnecting requires the Microsoft sign-in flow again.

Input Schema

Name	Required	Description	Default
`account`	No	The account to disconnect: its email (upn), id, or display name. Required when more than one account is connected.
`confirm`	No	Ignored; kept for older clients.

Output Schema

Name	Required	Description
`effect`	No	removes_credential: the stored sign-in is removed. turns_off: the account stops being read in Local MCP and stays signed in to its app.
`status`	Yes	disconnected or not_connected.
`account`	No
`message`	Yes
`account_id`	No
`remaining_accounts`	No	Other accounts of this service that stay connected.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

changedOutput schema / properties / status / description

Previous value: -"preview, disconnected or not_connected."New value: +"disconnected or not_connected."

Changed1 schema field changedOct 24, 2026

changedInput schema / properties / confirm / description

Previous value: -"Must be true to disconnect. Without it the call returns a preview and changes nothing."New value: +"Ignored; kept for older clients."

Changed10 schema fields changedOct 22, 2026

addedInput schema / properties / confirm

Added value: +{
+  "description": "Must be true to disconnect. Without it the call returns a preview and changes nothing.",
+  "type": "boolean"
+}

addedOutput schema / additionalProperties
```
Added value: +true
```
addedOutput schema / properties / account
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / account_id
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / default_account
```
Removed value: -{
-  "type": "string"
-}
```

addedOutput schema / properties / effect

Added value: +{
+  "description": "removes_credential: the stored sign-in is removed. turns_off: the account stops being read in Local MCP and stays signed in to its app.",
+  "type": "string"
+}

removedOutput schema / properties / ok

Removed value: -{
-  "type": "boolean"
-}

addedOutput schema / properties / remaining_accounts

Added value: +{
+  "description": "Other accounts of this service that stay connected.",
+  "type": "integer"
+}

addedOutput schema / properties / status

Added value: +{
+  "description": "preview, disconnected or not_connected.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "ok",
-  "message"
-]New value: +[
+  "status",
+  "message"
+]

Changed3 schema fields changedOct 5, 2026

addedInput schema / properties / account

Added value: +{
+  "description": "The account to disconnect: its email (upn), id, or display name. Required when more than one account is connected.",
+  "type": "string"
+}

addedOutput schema / properties / default_account
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / required

Added value: +[
+  "ok",
+  "message"
+]

First observedJun 30, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Adds substantial behavior beyond the destructiveHint annotation: stored sign-in is removed, default reassignment happens automatically to the oldest remaining account, the response reports the new default, and reconnecting requires the Microsoft sign-in flow again. These are exactly the consequences an agent needs before invoking a destructive disconnect.

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?

Front-loads the core action, then covers parameter requirements, default reassignment, and reconnection consequences in four compact sentences. Every sentence contributes useful information without repetition.

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

Completeness5/5

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

For a two-parameter destructive disconnect with full schema coverage and an output schema, the description covers the key operational facts: scope, account selection, default-account side effect, and reconnect requirement. No material information is missing.

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 100%, so the schema already documents both parameters including accepted account identifiers and the confirm field being ignored. The description reinforces when account is required or optional but adds little beyond the schema, making the baseline 3 appropriate.

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?

States a specific verb and resource (disconnects a Microsoft 365 account) and immediately scopes it to ONE account while noting that stored sign-in is removed. This clearly separates it from connect_m365_account and from broader account-management siblings.

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 key usage condition: account can be omitted only when one account is connected and must be provided when several are connected. It does not explicitly name alternatives such as list_m365_accounts for discovery, but the conditional guidance is clear and directly actionable.

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

All Local MCP tools Inspect

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.