Local MCP

Disconnect Microsoft 365 Account

disconnect_m365_account

Disconnect ONE Microsoft 365 account and remove 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. Runs immediately, with no preview or confirm step; reconnecting requires the Microsoft sign-in flow again. Only runs on the computer itself, not through the cloud connector.

Input Schema

TableJSON 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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`message`	Yes
`default_account`	No

Schema Changelog

Changes observed during successful MCP inspections.

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.7/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses that it runs immediately with no preview or confirm step, that the default-account role is reassigned to the oldest remaining account, and that reconnecting requires re-authentication. These are exactly the behavioral traits an agent needs before invoking a disruptive operation.

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 layers scope, parameter rules, side effects, and environment constraint. Every sentence carries distinct information with no filler.

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?

Given an output schema exists, return values need not be detailed, and the description still notes the answer reports the new default. Covers single-parameter semantics, side effects, confirmation behavior, and the local-only constraint, leaving no gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it clarifies the accepted identifier forms (email/upn, id, display name) and the conditional optionality (omittable with one account, required with several), which sharpens how the agent should populate the field.

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 ('Disconnect ONE Microsoft 365 account and remove its stored sign-in') with clear scope ('ONE'), distinguishing it from the connect_* and set_default_m365_account siblings. An agent immediately knows what the 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?

Gives explicit conditional usage for the account parameter ('with only one account connected it can be omitted, with several it must be given') and warns that reconnecting requires the sign-in flow again. It does not name sibling alternatives (e.g., set_default_m365_account, list_m365_accounts), so it stops short of a full when/when-not routing.

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.