Skip to main content
Glama
MadLlama25

Fastmail MCP Server

by MadLlama25

get_thread

Retrieve all emails in a conversation thread by providing the thread ID. Solves the need to view complete email threads for context.

Instructions

Get all emails in a conversation thread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
threadIdYesID of the thread/conversation

Implementation Reference

  • src/index.ts:809-822 (registration)
    Tool registration: 'get_thread' is registered in the ListToolsRequestSchema handler with name, description, and input schema requiring 'threadId'.
    {
      name: 'get_thread',
      description: 'Get all emails in a conversation thread',
      inputSchema: {
        type: 'object',
        properties: {
          threadId: {
            type: 'string',
            description: 'ID of the thread/conversation',
          },
        },
        required: ['threadId'],
      },
    },
  • Handler/switch-case: The 'get_thread' case in CallToolRequestSchema extracts threadId, validates it, calls client.getThread(threadId), and returns the result with error handling.
    case 'get_thread': {
      const { threadId } = args as any;
      if (!threadId) {
        throw new McpError(ErrorCode.InvalidParams, 'threadId is required');
      }
      const client = initializeClient();
      try {
        const thread = await client.getThread(threadId);
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(thread, null, 2),
            },
          ],
        };
      } catch (error) {
        // Provide helpful error information
        throw new McpError(ErrorCode.InternalError, `Thread access failed: ${redactBearerTokens(error instanceof Error ? error.message : String(error))}`);
      }
    }
Behavior2/5

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

No annotations provided. Description lacks behavioral details like pagination, limits, or whether attachments are included. Does not disclose any side effects or constraints beyond the basic action.

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?

Single sentence with no waste. Front-loads the core action efficiently.

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?

For a simple tool with one parameter and no output schema, the description is adequate but could mention return format or ordering. Not overly incomplete but leaves gaps.

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?

Schema coverage is 100% and description does not add meaning beyond the schema's 'ID of the thread/conversation'. Baseline 3 applies with no extra value.

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?

Description is a specific verb+resource: 'Get all emails in a conversation thread'. It clearly distinguishes from sibling tools like get_email (single email) and list_emails (list with filters).

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 like get_email or search_emails. No exclusions or prerequisites mentioned.

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