Skip to main content
Glama
Sign In
cfu_mail

cfu_mail

by MrShurukan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

account_logout

Revoke access and automatic login for a stored mail profile across local MCP processes by account ID.

Instructions

Disable access and automatic login for this profile across local MCP processes.

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": {
      "account_id": "<account_id>"
    },
    "name": "account_logout"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is covered; the description usefully adds that the effect spans local MCP processes and kills automatic login. However, it omits whether credentials/tokens are revoked, whether re-login is possible afterward, or whether in-flight sessions are terminated.

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 tight sentence with the effect front-loaded and no filler. It could be one clause longer to cover the parameter without bloat.

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 one-parameter session tool with annotations covering safety and no output schema, the description is adequate but leaves the identifier semantics and post-logout state unexplained, which an agent needs before invoking a logout.

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

Parameters2/5

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

Schema coverage is 0% and the single required parameter account_id has no description anywhere. The phrase 'this profile' only loosely implies the parameter is a profile/account identifier; it does not say what form the id takes or how to obtain it.

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 effect ('Disable access and automatic login') on a specific resource ('this profile') with a stated scope ('across local MCP processes'). It is distinguishable from siblings like account_status and account_switch, though it never names the logout/re-login counterpart behavior.

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 scope phrase 'across local MCP processes' implies when this is relevant (local session teardown rather than remote account deletion), but there is no explicit when-to-use, when-not-to-use, or reference to account_switch as the inverse operation.

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