Skip to main content
Glama
Mail-MCP

Mail-MCP

by Rixtayz

Sign in to Outlook

mail_login
Idempotent

Signs the user in to their personal Outlook mailbox when access is missing or expired, opening Microsoft sign-in in the browser with read and organize permissions only, never send email.

Instructions

Sign the user in to their personal Outlook mailbox. Call it when any other tool answers "Not signed in" or that the sign-in has expired. It opens a Microsoft sign-in page in the user's browser and waits for them to finish. If the result is "pending", ask the user to complete the sign-in in their browser, then call mail_login again. It asks for access to read and organize mail only: it never asks for permission to send email. Safe to call when already signed in.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
urlNo
detailYes
statusYes
accountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.2

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare this is not read-only, is idempotent, and is open-world, and the description adds the operational behavior those hints cannot convey: a browser page is opened, the call waits for the user, a 'pending' result is possible, and the requested scope is read/organize mail only with no send permission. This is exactly the added context annotations cannot supply.

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?

Front-loaded with the purpose, then the trigger, then the pending-result procedure and scope caveat; each sentence is functional. Minor awkwardness in the phrasing of the 'Not signed in' trigger clause keeps it below a 5.

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 an interactive authentication tool, the description covers the trigger, the blocking/browser behavior, the non-terminal 'pending' outcome that requires re-invocation, and the permission scope. An output schema exists, so return-value explanation is unnecessary, and nothing an agent needs in order to call it correctly 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond what the empty schema already shows. A 4 is the appropriate baseline for a parameterless tool.

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?

States a specific verb and resource ('Sign the user in to their personal Outlook mailbox') and is clearly distinguishable from the sibling mail_logout. An agent knows exactly what capability this provides without reading any schema.

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?

Gives an explicit trigger condition ('when any other tool answers "Not signed in" or that the sign-in has expired'), an explicit safe-to-call case ('Safe to call when already signed in'), and a retry procedure for the pending case. No inference required.

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