Skip to main content
Glama
cfu_mail

cfu_mail

account_switch

Switch to an existing signed-in mail account; logged-out accounts must complete local sign-in before use.

Instructions

Choose an already signed-in profile. Logged-out profiles require local sign-in.

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

Input Schema

NameRequiredDescriptionDefault
account_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the description's added value is the authentication-state precondition, which is genuinely useful. It does not say what happens to the previously active profile/session, whether the switch persists, or what a success response looks like — gaps that matter for a state-changing call.

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?

Two short sentences, no filler, with the core action front-loaded ahead of the caveat. Appropriately sized for a single-parameter tool.

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, no-output-schema tool the description covers the essential precondition, but it leaves the agent without the identifier's origin and without any statement of the effect of switching. Slightly under-complete for a state-mutating session operation.

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

Parameters3/5

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

There is one required parameter with 0% schema description coverage, so the description must carry the burden; saying "choose a profile" does implicitly map account_id to a profile identifier. It gives no format, no source (e.g., obtain it from account_status), and no guidance on valid values.

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?

"Choose an already signed-in profile" gives a concrete verb and resource, and the word "profile" plus "switch" makes it distinguishable from siblings like account_logout and account_status. It stops short of explicitly naming those siblings or stating what makes this different from them beyond the sign-in constraint.

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 second sentence establishes a real precondition (the target profile must already be signed in, otherwise local sign-in is needed), which tells the agent when this call will fail. However, it never names alternatives (e.g., account_status to find an eligible profile, account_logout to change context) or states when-not to call it.

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