Skip to main content
Glama

list_all_accounts

Read-onlyIdempotent

Lists all configured email accounts and their capabilities (IMAP, SMTP, Graph API, EWS), helping you select the correct read and send tools per account.

Instructions

List all configured email accounts with their capabilities (IMAP, SMTP, Graph API, EWS). Use this to know which send/read tools to use per account.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYesTool-specific data payload
metaYesExecution metadata (timestamp, duration)
summaryYesHuman-readable summary of the operation outcome

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.12

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered upstream. The description adds only that each account is returned with its protocol capabilities, which is largely restated by the existing output schema, and says nothing about behavior when no accounts are configured.

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, front-loaded with the resource and result shape, followed by the routing rationale. Every clause carries information and there is no filler or repetition.

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 zero parameters, a full output schema, and complete annotations, the description covers everything an agent needs to decide to call it and how to interpret the result. It stops short of noting edge cases such as an empty account list or how to proceed when a protocol is unavailable.

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?

The tool takes zero parameters, which is the baseline-4 case, but there is genuinely nothing for the description to clarify about inputs. The mid-range score reflects that the description adds no input-related meaning beyond confirming the tool is parameterless by describing a global list.

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 verb and resource ('List all configured email accounts') and enumerates what is returned (IMAP, SMTP, Graph API, EWS capabilities). It is clear enough to act on without opening the schema, though it never explicitly contrasts itself with the sibling imap_list_accounts, so the agent must infer that this one spans all backends.

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?

Provides a concrete use case: 'Use this to know which send/read tools to use per account,' which tells the agent this is a discovery/routing step before calling send or read tools. It gives no when-not guidance or named exclusions (e.g. versus imap_list_accounts or imap_verify_account), but the positive guidance is unambiguous.

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