Skip to main content
Glama

graph_auth_login

Authenticate to Microsoft 365 using OAuth2 via browser or device code, granting access to Graph MCP tools for Teams, Outlook, OneDrive, and related collaboration services.

Instructions

Log in to Microsoft 365. Opens a browser for OAuth2 authentication.

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": "graph_auth_login"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodNobrowser

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses a side effect, a browser window opening, which is real behavioral context. But it says nothing about token caching/persistence, session lifetime, whether an existing session is reused, or what happens on failure.

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?

Two short, front-loaded sentences with no filler. It is efficient; the brevity is under-specification rather than verbosity, so conciseness itself is fine.

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

Completeness3/5

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

For a simple one-optional-parameter auth tool with no output schema, this is minimally viable. It omits how the device_code flow behaves and what state the tool leaves behind, both of which an agent needs to choose a method correctly.

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

Parameters2/5

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

Schema description coverage is 0% for the single 'method' parameter, and the description only half compensates: 'Opens a browser' maps to the browser default but the device_code alternative is never explained (no hint that it is for headless/no-browser environments or that the user must visit a URL and enter a code).

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?

States a specific verb and resource: 'Log in to Microsoft 365' with OAuth2 as the mechanism. It is clearly distinct from graph_auth_logout and graph_auth_status by plain meaning, though it never names them.

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: an agent can infer it must authenticate before other graph_* calls. There is no explicit when-to-use, no prerequisite statement (e.g. whether a client/app registration is required), and no mention of calling graph_auth_status afterward to verify.

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