Skip to main content
Glama
Sign In
cfu_mail

cfu_mail

by MrShurukan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

account_status

Read-only

Lists saved mail profiles and identifies the active account without connecting or revealing secrets, helping verify account context before mail actions.

Instructions

List saved profiles and active account. Does not connect or reveal secrets.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly=true, destructive=false; the description adds value by stating no connection is made and no secrets are exposed, which is the key safety information an agent needs when handling credential-adjacent tools. Slight tension with openWorldHint=true (a local-only operation) is not resolved but is not a contradiction.

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, zero waste, with the core purpose front-loaded and the caveat second.

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

Completeness4/5

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

With no output schema, the description usefully names what is returned (saved profiles, active account) and what is not (secrets, live connection). It could be marginally richer about whether profiles include account identifiers, but is sufficient to invoke correctly.

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?

Zero parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate.

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?

Specific verb + resource: 'List saved profiles and active account' tells the agent exactly what comes back. It is naturally distinguishable from account_switch/account_logout siblings, though it never names them 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?

'Does not connect or reveal secrets' gives a useful negative constraint (this is a local, non-connecting read, not a connection test), but there is no positive guidance on when to prefer it over account_switch or connection_check.

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