Skip to main content
Glama
Mail-MCP

Mail-MCP

by Rixtayz

Sign out of Outlook

mail_logout
Idempotent

Sign out by removing the stored sign-in from this computer; mail tools stop working until login is called again, and the result includes a Microsoft link to withdraw access.

Instructions

Sign the user out: removes the sign-in stored on this computer. Mail tools stop working until mail_login is called again. The result includes a link where the user can also withdraw Mail-MCP's access on Microsoft's side.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
detailYes
accountNo
revokeUrlYes
signedOutYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.2

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare the non-read-only, non-destructive, idempotent profile; the description adds the substantive behavior an agent actually needs — that the stored sign-in on this machine is removed, that all mail tools become unusable until re-login, and that the response carries a Microsoft-side access revocation link. This is meaningful context beyond the annotation set and is consistent with it (mutation, but not destructive of user data).

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?

Three short sentences, front-loaded with the action, then the consequence, then the return-value nuance. Every sentence carries distinct information with no repetition of the title or schema.

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, well-annotated tool with an output schema, the description covers everything an agent needs: the effect, the downstream impact on sibling tools, the recovery path, and a pointer to the extra affordance in the result. Nothing material is missing.

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 there is no parameter semantics to document, which is the baseline-4 case. The description correctly spends no space on inputs.

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?

"Sign the user out: removes the sign-in stored on this computer" gives a specific verb and resource, and immediately clarifies the scope of the action. The follow-up sentence names mail_login as the counterpart, so an agent can distinguish this from the sibling login tool without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the operating condition explicit: mail tools stop working until mail_login is called again, which tells an agent both when to use this and what must follow it. It stops short of stating exclusions or prerequisites (e.g., what happens if no session exists), which keeps it from a 5.

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