Skip to main content
Glama

graph_auth_status

Checks Microsoft Graph authentication status and attempts a token refresh when needed, helping confirm access before running Teams, Outlook, or OneDrive operations.

Instructions

Check Microsoft Graph authentication status. Attempts token refresh if needed.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. It does disclose one non-obvious side effect — that a call may attempt a token refresh, meaning this 'check' is not purely passive — which is genuinely useful. However, it is silent on failure behavior: whether it throws, returns a false status, triggers an interactive login prompt, or how long a refresh attempt may block.

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?

Two short sentences with zero filler, and the core purpose is front-loaded before the side-effect caveat. Nothing could be cut without losing information.

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 trivial zero-parameter tool this is nearly sufficient, but there is no output schema, so the description should say what a status check yields (boolean authenticated flag, account identity, token expiry, error shape). Without that, an agent cannot anticipate the return value or branch on it.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter-level meaning is missing.

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: 'Check Microsoft Graph authentication status.' An agent can tell this apart from graph_auth_login and graph_auth_logout by the verb alone, though the description never names those siblings explicitly.

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 would infer it should call this before an authenticated Graph operation. There is no explicit when-to-use, no guidance on what to do if it reports unauthenticated (e.g., route to graph_auth_login), and no stated prerequisites.

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