Skip to main content
Glama
owen-nash

Fastmail MCP Server

by owen-nash

get_account_summary

Retrieve an overall Fastmail account summary with key statistics to quickly assess account activity and status.

Instructions

Get overall account summary with statistics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:840-846 (registration)
    Tool registration for get_account_summary in the ListToolsRequestSchema handler. No input parameters.
      name: 'get_account_summary',
      description: 'Get overall account summary with statistics',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Handler that calls client.getAccountSummary() and returns the result as JSON.
    case 'get_account_summary': {
      const client = initializeClient();
      const summary = await client.getAccountSummary();
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(summary, null, 2),
          },
        ],
      };
    }
  • Actual implementation of getAccountSummary() on JmapClient. Fetches session, mailboxes, and identities, then computes totals (totalEmails, unreadEmails, totalThreads, unreadThreads) and returns a summary with mailbox details.
    async getAccountSummary(): Promise<any> {
      const session = await this.getSession();
      const mailboxes = await this.getMailboxes();
      const identities = await this.getIdentities();
    
      // Calculate totals
      const totals = mailboxes.reduce((acc, mb) => ({
        totalEmails: acc.totalEmails + (mb.totalEmails || 0),
        unreadEmails: acc.unreadEmails + (mb.unreadEmails || 0),
        totalThreads: acc.totalThreads + (mb.totalThreads || 0),
        unreadThreads: acc.unreadThreads + (mb.unreadThreads || 0)
      }), { totalEmails: 0, unreadEmails: 0, totalThreads: 0, unreadThreads: 0 });
    
      return {
        accountId: session.accountId,
        mailboxCount: mailboxes.length,
        identityCount: identities.length,
        ...totals,
        mailboxes: mailboxes.map(mb => ({
          id: mb.id,
          name: mb.name,
          role: mb.role,
          totalEmails: mb.totalEmails || 0,
          unreadEmails: mb.unreadEmails || 0
        }))
      };
    }
Behavior2/5

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

With no annotations, the description must disclose behavior. It only says 'get' and 'statistics', but doesn't confirm read-only nature, required permissions, or side effects. This is minimal.

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?

The description is only 6 words, efficient but front-loaded. No wasted words, but could be expanded slightly for clarity.

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

Completeness2/5

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

No output schema, and description barely hints at return value ('statistics'). For a tool with no params, more context on what statistics are included would improve completeness.

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?

Input schema has zero parameters, so description adds no param info. Baseline is 4 because there's nothing to add beyond schema.

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 action ('Get') and the resource ('overall account summary'), adding 'with statistics' to hint at the content. However, it doesn't differentiate from sibling tools like 'get_mailbox_stats', which may overlap.

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?

No guidance on when to use this tool versus alternatives (e.g., get_mailbox_stats or list_mailboxes). The description lacks context about prerequisites or use cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/owen-nash/fastmail-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server