Skip to main content
Glama

Switch Account

switch_account
Destructive

Changes the default Microsoft 365 account used for subsequent tool calls so requests target the selected account. Provide an account ID to switch context without reconfiguring the server.

Instructions

Switch the default account for subsequent tool calls

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": {
      "account_id": "<account_id>"
    },
    "name": "switch_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYesAccount ID to set as default

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the phrase 'for subsequent tool calls' correctly corroborates that this is a persistent state mutation. What is missing is the behavior an agent actually needs: whether the account must already be authenticated or resolvable, what happens if the ID is invalid, whether the change is reversible, and how to restore the previous default.

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?

A single front-loaded sentence with no wasted words, and the scoping qualifier is placed where it matters. It is efficient, though for a global state mutation the terseness borders on underspecification rather than model concision.

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?

This tool silently changes the identity used by every subsequent call, yet the description supplies no information on discovering valid account IDs, on failure semantics, or on reverting. With no output schema and annotations covering only the destructive flag, the description leaves real operational gaps for a global-scope mutation.

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% for the single required account_id parameter, so the schema already states it is the account to set as default. The description adds no meaning beyond that — no indication of whether the value is an opaque ID versus an email/UPN, or where a valid ID can be obtained (e.g. via an account-listing or auth-status call).

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?

Names a specific verb and resource — 'Switch the default account' — and scopes it with 'for subsequent tool calls', so the agent knows the effect is persistent across later invocations rather than limited to one request. It does not name any sibling (e.g. get_auth_status) to distinguish itself, which keeps it short of a 5.

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?

Usage is only implied: the agent must infer that this is called before doing work under a different identity. There is no guidance on when not to use it, no mention of checking the current account or auth state first, and no pointer to the auth-status sibling as an alternative for read-only inspection.

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