Skip to main content
Glama

summarize_email

Extract key points from Outlook emails to quickly understand content without reading full messages. Use this tool to identify important information and action items from individual emails.

Instructions

Summarize individual email content

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
email_idYesEmail ID to summarize

Implementation Reference

  • src/index.ts:57-70 (registration)
    Registration of the 'summarize_email' MCP tool including name, description, and input schema requiring 'email_id'.
    {
      name: "summarize_email",
      description: "Summarize individual email content",
      inputSchema: {
        type: "object",
        properties: {
          email_id: {
            type: "string",
            description: "Email ID to summarize"
          }
        },
        required: ["email_id"]
      }
    },
  • Handler for the 'summarize_email' tool: validates input, fetches email using OutlookManager, generates and returns a formatted text summary.
    case 'summarize_email': {
      const emailId = (args as any)?.email_id;
      if (!emailId) {
        throw new Error('Email ID is required');
      }
      const email = await outlookManager.getEmailById(emailId);
      return {
        content: [
          {
            type: 'text',
            text: `📧 **Email Details**\n\n**Subject:** ${email.subject}\n**From:** ${email.sender}\n**To:** ${email.recipients?.join(', ')}\n**Time:** ${email.receivedTime}\n**Read:** ${email.isRead ? 'Yes' : 'No'}\n\n**Content Summary:**\n${email.body?.substring(0, 500)}${email.body && email.body.length > 500 ? '...' : ''}`,
          },
        ],
      };
    }
  • Advanced email summarization helper function (not directly used in main handler) that extracts key info, detects priority/action, generates formatted summary.
    static summarizeEmail(email: EmailMessage): string {
      const summary = {
        subject: email.subject,
        sender: email.sender,
        receivedTime: email.receivedTime,
        isRead: email.isRead,
        hasAttachments: email.hasAttachments,
        bodyPreview: this.extractBodyPreview(email.body),
        keyPoints: this.extractKeyPoints(email.body),
        priority: this.detectPriority(email.subject, email.body),
        actionRequired: this.detectActionRequired(email.body)
      };
    
      return this.formatSummary(summary);
    }
  • Alternative handler in index_new.js that uses EmailSummarizer.summarizeEmail for advanced summary.
    case 'summarize_email': {
        const email = await outlookManager.getEmailById(args.email_id);
        const summary = EmailSummarizer.summarizeEmail(email);
        return {
            content: [
                {
                    type: 'text',
                    text: summary,
                },
            ],
        };
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. It states what the tool does but doesn't describe how it works—for example, whether it generates a new summary each time, what format or length the summary has, or if it requires specific permissions. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place, and there's no redundancy or fluff.

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?

Given the lack of annotations and output schema, the description is incomplete for a tool that performs a non-trivial operation like summarization. It doesn't explain what the summary output looks like, any limitations (e.g., length, language), or error conditions. For a tool with no structured output documentation, the description should provide more context about the result.

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?

The input schema has 100% description coverage, with the single parameter 'email_id' clearly documented. The description doesn't add any meaning beyond the schema, such as explaining what constitutes a valid email ID or where to obtain it. However, with high schema coverage and only one parameter, the baseline score of 3 is appropriate as the schema handles the documentation adequately.

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 ('Summarize') and resource ('individual email content'), making the purpose immediately understandable. It doesn't explicitly differentiate from the sibling 'summarize_inbox' tool, which appears to summarize multiple emails, but the focus on 'individual' provides some distinction. The description avoids tautology by specifying the action beyond just the tool name.

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. It doesn't mention the sibling 'summarize_inbox' tool for bulk summarization or clarify prerequisites like needing an email ID. There's no indication of when this tool is appropriate versus simply reading the email with 'get_email_by_id'.

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/cqyefeng119/windows-outlook-mcp'

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