list_accounts

View configured email and calendar accounts on macOS to enable AI agents to access your Mail and Calendar data locally.

Instructions

List configured email and calendar accounts

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Implementation Reference

server.js:73-86 (registration)

The 'list_accounts' tool is registered in the TOOLS array (line 74) and then all tools are registered with the MCP server using server.tool() in a loop (lines 82-86). This is a stub implementation that returns a message directing users to install the real Pilot MCP server on macOS.

  ["list_safari_bookmarks", "List Safari bookmarks"],
  ["list_accounts", "List configured email and calendar accounts"],
  ["create_email_folder", "Create a new email folder/mailbox"],
  ["diagnose", "Run diagnostic checks on all connected services"],
  ["report_bug", "Report a bug or issue to the development team"],
  ["request_feature", "Request a new feature"],
  ["request_integration", "Request integration with an unsupported app"],
];

for (const [name, desc] of TOOLS) {
  server.tool(name, desc, {}, async () => ({
    content: [{ type: "text", text: "This is an inspection stub. Install Pilot MCP on macOS: npx -y local-mcp@latest setup" }],
  }));
}

Tool Definition Quality

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to specify what 'configured' entails, what fields are returned (account IDs, names, types), or whether disabled accounts are included. It only implies a read-only operation through the verb 'List'.

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?

The description is a single efficient sentence with no redundant words. It immediately states the tool's function without preamble or unnecessary elaboration.

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?

Given the tool's simplicity and lack of parameters, the description is minimally adequate. However, without an output schema, it could improve by indicating what account information is returned (e.g., identifiers, account names) to help the agent use the results in subsequent tool calls.

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 input schema contains zero parameters, establishing a baseline score of 4. The description correctly implies no filtering or input is required to retrieve the full list of accounts.

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?

The description clearly states the verb (List) and resource (configured email and calendar accounts). It implicitly distinguishes itself from siblings like list_emails and list_calendar_events by focusing on account configuration rather than content, though it doesn't explicitly clarify this distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention the typical discovery pattern (using this to identify account IDs before querying specific emails or events).

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

Install Server

Pilot MCP

list_accounts

Instructions

Input Schema

Implementation Reference

Tool Definition Quality

Other Tools

Latest Blog Posts

MCP directory API