Skip to main content
Glama

Set Access Token

set_access_token
Destructive

Sets or updates the Microsoft Graph access token for client-token authentication so Microsoft 365 requests can run without interactive sign-in.

Instructions

Set or update the access token (client-token auth mode only)

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
expires_onNoToken expiration time in ISO format
access_tokenYesThe access token for Microsoft Graph

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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, so the write/destructive nature is covered structurally. The description adds the useful constraint that this only applies in client-token auth mode, but says nothing about what happens to an existing token (overwrite), whether subsequent requests pick it up immediately, or validation/error behavior for a credential-mutating operation.

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 short sentence with the core action front-loaded and no filler. It is efficient, though the parenthetical qualifier carries a lot of unexpanded weight.

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?

The tool is simple (two fully documented parameters, no output schema), so little is required. However, as a destructive credential-setting operation, the description omits consequences and prerequisites that an agent would want before overwriting auth state.

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%, so both access_token and expires_on are already documented in the schema, including the ISO format and Microsoft Graph scope. The description adds no parameter meaning beyond the schema, so the baseline of 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 gives a specific verb pair ('Set or update') and resource ('the access token'), plus a scope qualifier ('client-token auth mode only'). An agent can distinguish this from read-only auth tools such as get_auth_status without opening the schema, though the sibling is not named.

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?

The parenthetical '(client-token auth mode only)' is a real precondition that implies when the tool applies, but there is no explicit when-not guidance and no pointer to get_auth_status for checking existing auth state first. Usage is implied rather than stated.

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