Skip to main content
Glama
MadLlama25

Fastmail MCP Server

by MadLlama25

get_account_summary

Obtain an overall account summary with statistics to assess Fastmail email, contacts, and calendar usage.

Instructions

Get overall account summary with statistics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The getAccountSummary method on JmapClient: fetches the session, all mailboxes, and all identities; computes aggregate email/thread totals; returns accountId, mailboxCount, identityCount, totals, and per-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
        }))
      };
    }
  • Schema registration for the get_account_summary tool: no input parameters required, returns account statistics.
      name: 'get_account_summary',
      description: 'Get overall account summary with statistics',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • src/index.ts:1623-1634 (registration)
    Registration/call handler for get_account_summary in the CallToolRequestSchema switch statement. Calls client.getAccountSummary() and returns the result as JSON text.
    case 'get_account_summary': {
      const client = initializeClient();
      const summary = await client.getAccountSummary();
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(summary, null, 2),
          },
        ],
      };
    }
Behavior2/5

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

No annotations are provided, and the description does not disclose whether the tool is read-only, destructive, or involves external side effects. The verb 'Get' suggests a read operation, but this is not explicitly stated.

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 sentence with no wasted words. It efficiently conveys the core functionality.

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?

For a tool with no parameters and no output schema, the description is minimal. It omits key details such as what statistics are included or whether the summary reflects real-time data. An agent may need more context to correctly interpret the result.

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 has zero parameters with 100% coverage. The description adds the context 'with statistics', providing slight semantic value beyond the schema. Baseline for zero parameters is 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The tool name and description explicitly state that it retrieves an account summary with statistics, which is distinct from all sibling tools that focus on emails, contacts, or calendars. This leaves no ambiguity about what the tool does.

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?

No explicit guidance on when or why to use this tool over alternatives. Since it is the only tool for account-level overview, usage is implied but not articulated.

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/MadLlama25/fastmail-mcp'

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