Skip to main content
Glama
lobster-kit

mcp-server-lobstermail

by lobster-kit

Check Inbox

check_inbox

List recent emails in a LobsterMail inbox to view sender, subject, and preview content for monitoring or processing messages.

Instructions

List recent emails in an inbox. Returns sender, subject, and preview for each email.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inbox_idYesInbox ID (e.g. ibx_...)
limitNoMax emails to return (default: 20)
sinceNoOnly emails after this ISO 8601 timestamp

Implementation Reference

  • Implementation of the 'check_inbox' MCP tool, which lists recent emails in an inbox.
    server.registerTool('check_inbox', {
      title: 'Check Inbox',
      description: 'List recent emails in an inbox. Returns sender, subject, and preview for each email.',
      inputSchema: {
        inbox_id: z.string().describe('Inbox ID (e.g. ibx_...)'),
        limit: z.number().optional().describe('Max emails to return (default: 20)'),
        since: z.string().optional().describe('Only emails after this ISO 8601 timestamp'),
      },
    }, async ({ inbox_id, limit, since }) => {
      const inbox = await getInbox(inbox_id);
      const emails = await inbox.receive({ limit, since });
    
      if (emails.length === 0) {
        return { content: [{ type: 'text' as const, text: 'No emails found in this inbox.' }] };
      }
    
      const lines = emails.map(
        (e) =>
          `- [${e.id}] From: ${e.from} | Subject: ${e.subject} | ${e.createdAt}` +
          (e.isInjectionRisk ? ' ⚠️ INJECTION RISK' : ''),
      );
    
      return {
        content: [
          {
            type: 'text' as const,
            text: `${emails.length} email(s) found:\n\n${lines.join('\n')}\n\nUse get_email with an email_id to read the full body.`,
          },
        ],
      };
    });
Behavior3/5

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

No annotations provided, so description carries full burden. It compensates partially by disclosing return fields (sender, subject, preview) which substitutes for missing output schema. However, lacks details on sorting order (chronological?), pagination behavior, rate limits, or whether 'recent' implies a server-side default when 'since' is omitted.

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?

Two sentences, zero waste. First sentence establishes purpose and scope, second discloses return structure. Information is front-loaded and appropriately sized for the tool's complexity.

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

Completeness4/5

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

Given 3 well-documented parameters and no output schema, the description adequately covers the essential contract by listing return fields. Only significant gap is the lack of sibling differentiation guidance; otherwise complete for a read-only list operation.

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 has 100% description coverage (inbox_id format, limit default, since format), establishing baseline 3. Description adds minimal semantic value beyond schema—'recent' loosely implies the 'since' parameter's purpose but doesn't clarify syntax, validation rules, or parameter interactions.

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?

Clear verb 'List' + resource 'emails' + scope 'inbox'. The description effectively distinguishes from siblings: uses plural 'emails' vs 'get_email' (singular), 'recent' implies temporal listing vs 'search_emails' (filtering), and specifies 'inbox' vs 'list_inboxes' (which lists inboxes, not emails).

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 vs alternatives like 'search_emails' (filtering vs listing), 'get_email' (single vs batch), or 'list_threads' (thread-centric vs email-centric). No mention of workflow prerequisites or when to use 'since' vs retrieving all recent.

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/lobster-kit/mcp-server-lobstermail'

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