Skip to main content
Glama
as-j

Fastmail MCP Server

by as-j

list_identities

Read-onlyIdempotent

Retrieve all Fastmail sending identities and aliases to select the correct sender address before composing or sending an email. Ensures only allowed from addresses are used.

Instructions

List Fastmail sending identities that can be used in the from field. Use before send_email, save_draft, or create_draft when the user wants to send from an alias or confirm which sender addresses are allowed. Do not use for inbox or message retrieval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for 'list_identities' tool — calls client.getIdentities() and returns the result as JSON text.
    case 'list_identities': {
      const identities = await client.getIdentities();
      return { content: [{ type: 'text', text: JSON.stringify(identities, null, 2) }] };
  • Helper function getIdentities() in the JMAP client — makes an Identity/get JMAP call to fetch sending identities.
    async getIdentities(): Promise<any[]> {
      const session = await this.getSession();
      
      const request: JmapRequest = {
        using: ['urn:ietf:params:jmap:core', 'urn:ietf:params:jmap:submission'],
        methodCalls: [
          ['Identity/get', {
            accountId: session.accountId
          }, 'identities']
        ]
      };
    
      const response = await this.makeRequest(request);
      return this.getListResult(response, 0);
    }
  • Schema definition for 'list_identities' tool — no input parameters (emptySchema), returns list of sending identities.
      'list_identities',
      'List Sending Identities',
      description(
        'List Fastmail sending identities that can be used in the from field.',
        'Use before send_email, save_draft, or create_draft when the user wants to send from an alias or confirm which sender addresses are allowed.',
        'Do not use for inbox or message retrieval.',
      ),
      emptySchema,
    ),
  • Registration of 'list_identities' in the capabilities/availability listing under 'identity' functions.
    identity: {
      available: true,
      functions: ['list_identities'],
    },
Behavior3/5

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds minimal behavioral context beyond specifying the resource type (sending identities) but does not contradict annotations.

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?

Three concise sentences with no fluff. Main action front-loaded, usage guidance clear, and negative case provided.

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

Completeness5/5

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

With 0 parameters, no output schema, and high-quality annotations, the description fully covers the tool's purpose and usage context. No gaps.

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 0 parameters, so baseline 4. Description adds value by clarifying that the identities are for the 'from' field, but no parameter details needed.

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?

Clearly states 'List Fastmail sending identities that can be used in the from field,' specifying the verb (list) and resource (sending identities), and distinguishes from siblings by providing context about its use in sending email.

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

Usage Guidelines5/5

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

Explicitly states when to use: 'before send_email, save_draft, or create_draft when the user wants to send from an alias or confirm which sender addresses are allowed,' and includes a negative usage: 'Do not use for inbox or message retrieval.'

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

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