Skip to main content
Glama

set_access_token

Stores the Microsoft Graph API access token needed to authenticate Outlook email operations, enabling reading, searching, and managing messages.

Instructions

Set the Microsoft Graph API access token for Outlook access

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": {
      "access_token": "<access_token>"
    },
    "name": "set_access_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
access_tokenYesMicrosoft Graph API access token

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does not say where the token is stored, whether it overrides a previously set token, whether it is validated against Graph, how long it persists, or what an invalid token produces — all material for a credential-setting mutation.

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?

One short, front-loaded sentence with no filler. The brevity is appropriate, though the space saved is not spent on any of the missing behavioral context.

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 one-parameter setter with no output schema and no annotations, the description conveys the essential purpose. It omits the sequencing relationship to the sibling email tools and the effect on any existing token, which an agent needs to invoke it correctly.

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?

The single parameter has 100% schema description coverage, so the schema already defines access_token as a Microsoft Graph API access token. The description merely restates that, adding no format, scope, or permission-requirement detail beyond the schema; baseline 3 applies.

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 names a specific verb ("Set") and resource ("Microsoft Graph API access token") with the target system (Outlook) stated, so it is immediately distinguishable from the email-operation siblings. It does not, however, clarify whether this replaces an existing token or is a one-time bootstrap.

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 this must be called before the email tools (list_emails, get_email, etc.) will work, but the description never says so. There are no prerequisites, no token-expiry or re-authentication guidance, and no exclusions.

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