Skip to main content
Glama
Sign In
graphdo-ts

graphdo-ts

Official
by co-native-ab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Logout from Microsoft

logout
DestructiveIdempotent

Sign out of Microsoft Graph and clear cached tokens for secure session termination. To continue, use the login tool to re-authenticate.

Instructions

Sign out of Microsoft Graph and clear all cached tokens. After logging out, the login tool must be used to re-authenticate.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A4.9/5.0
Behavior5/5

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

The description discloses that cached tokens are cleared, adding behavioral detail beyond the annotations' destructive and idempotent hints. It aligns with annotations and explains the consequence of logout.

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 sentences, front-loaded with the verb and action, with no filler. Every sentence earns its place, providing the action, the effect, and the next step efficiently.

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

Completeness5/5

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

For a zero-parameter, no-output-schema tool, the description fully covers what the tool does, the effect on cached tokens, and the required next step. It is complete and self-contained.

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?

With zero parameters, the description appropriately focuses on behavior rather than parameter syntax. The schema already covers all (non-existent) parameters, so the baseline of 4 applies.

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?

The description clearly states the action ('Sign out of Microsoft Graph') and the resource affected, distinguishing it from sibling tools like login and auth_status. It is a specific verb+resource statement with no ambiguity.

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?

It explicitly specifies that after logging out, the login tool must be used to re-authenticate, providing a direct alternative and next-step guidance. This frames the tool's usage context clearly.

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