Skip to main content
Glama
outlook-mcp

outlook-mcp

by Plong-Wasin

auth_start

Starts Outlook authentication flow when an authentication error occurs or user requests re-authentication. Use only when needed, not proactively.

Instructions

Start the Outlook authentication flow. IMPORTANT: Only call this tool when you receive an authentication error (e.g. 'Not authenticated') from another tool, or when the user explicitly requests re-authentication. Do NOT call this proactively before using other Outlook tools — they automatically use the stored token. If a valid token already exists, this returns immediately without starting a new auth flow.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "auth_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoForce re-authentication even if a valid token exists (default: false)
clientIdNoAzure AD application client ID (optional, uses Microsoft Graph Explorer by default)
tenantIdNoAzure AD tenant ID (optional, uses 'common' by default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that a valid token causes an immediate no-op return, and that tokens are shared implicitly with sibling tools. It stops short of describing what a successful invocation produces (a URL, a device code, or an interactive prompt) and that a follow-up poll step is required, which matters for an auth flow.

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?

Purpose is front-loaded, then the usage constraint, then the no-op behavior — a sensible order with no filler sentences. The final sentence slightly overlaps the earlier 'they automatically use the stored token' point, but they address different actors (caller vs. tool).

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 zero-required-parameter auth tool with no annotations and no output schema, the description covers the critical decision of whether to call it at all. The main gap is what happens after invocation — whether the tool returns something needing user action and whether auth_poll must follow — which an agent would still have to discover.

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 force, clientId and tenantId are already documented in the schema, setting the baseline at 3. The description's remark about returning immediately when a valid token exists implicitly hints at the force parameter but never names or explains it, so no meaning is added beyond the schema.

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 ("Start the Outlook authentication flow") and immediately scopes it against the rest of the server by noting that other Outlook tools automatically use the stored token. An agent can tell this apart from the normal data tools without reading any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger (an authentication error such as 'Not authenticated', or an explicit user request) and an explicit prohibition (do not call proactively before other Outlook tools). This is exactly the when/when-not guidance that prevents wasted calls.

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