Skip to main content
Glama
Microsoft 365 MCP Server

Microsoft 365 MCP Server

by Softeria

select-account

Set a Microsoft account as the default for Microsoft 365 actions by providing its email address or account ID; use list-accounts to find available accounts.

Instructions

Select a Microsoft account as the default. Accepts email address (e.g. user@outlook.com) or account ID. Use list-accounts to discover available accounts.

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": "<account>"
    },
    "name": "select-account"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountYesEmail address or account ID of the account to select

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.131.2
  2. Removedv0.131.2
  3. Addedv0.114.0
  4. Removedv0.112.2
  5. Addedv0.110.0
  6. Removedv0.108.0
  7. Changed3 schema fields changedv0.96.0
    • addedInput schema / properties / account
      Added value: +{
      +  "description": "Email address or account ID of the account to select",
      +  "type": "string"
      +}
    • removedInput schema / properties / accountId
      Removed value: -{
      -  "description": "The account ID to select",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "accountId"
      -]New value: +[
      +  "account"
      +]
  8. First observedv0.31.0

TDQS

A3.8/5.0
Behavior3/5

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

The annotations declare readOnlyHint=false, so the agent knows this mutates state; the description confirms what is mutated (the default account selection). However, it does not say whether the selection persists across sessions, what happens on an invalid account, or whether it requires prior login — details that matter for a state-changing tool with only openWorldHint=false declared.

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?

Three short sentences, each earning its place: what it does, accepted input formats, and where to find valid values. The purpose is front-loaded in the first clause with zero preamble.

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 single-parameter, no-output-schema tool with clear annotations, the description covers purpose, input format, and discovery path. The only real omission is side-effect scope — whether the default applies to subsequent tool calls globally and how long it persists — which an agent would reasonably want before invoking.

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% and the schema itself already documents the single parameter as 'Email address or account ID of the account to select.' The description's example (user@outlook.com) and 'or account ID' largely restate that, adding format illustration but no new constraints. Baseline 3 applies when the schema carries the semantic load.

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 opens with a specific verb and resource: 'Select a Microsoft account as the default.' That is unambiguous and distinguishable from the sibling list-accounts, login, and remove-account by naming the account to be discovered. It stops short of explicitly contrasting with login/logout, so an agent still has to infer the auth-related boundary.

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?

It gives concrete usage context ('as the default') and points to a concrete alternative workflow: 'Use list-accounts to discover available accounts.' There are no exclusions or when-not guidance (e.g. what to do if the account is unknown, or whether login is a prerequisite), which keeps it below a 5.

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