Skip to main content
Glama
lobster-kit

mcp-server-lobstermail

by lobster-kit

Get Account Info

get_account

Retrieve LobsterMail account details such as tier level, usage limits, and statistics for managing email operations.

Instructions

Get account information including tier, limits, and usage stats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `get_account` tool is registered and implemented in src/index.ts. It calls the `getAccount()` method on the LobsterMail client retrieved via `getClient()`.
    server.registerTool('get_account', {
      title: 'Get Account Info',
      description: 'Get account information including tier, limits, and usage stats.',
      inputSchema: {},
    }, async () => {
      const lm = await getClient();
      const acct = await lm.getAccount();
    
      return {
        content: [
          {
            type: 'text' as const,
            text: [
              `Account: ${acct.id}`,
              `Tier: ${acct.tier} (${acct.tierName})`,
              `Can send: ${acct.limits.canSend}`,
              `Max inboxes: ${acct.limits.maxInboxes ?? 'unlimited'}`,
              `Daily email limit: ${acct.limits.dailyEmailLimit}`,
              `Inboxes used: ${acct.usage.inboxCount}`,
              `Total emails received: ${acct.usage.totalEmailsReceived}`,
              `Created: ${acct.createdAt}`,
            ].join('\n'),
          },
        ],
      };
    });
    
    // ── Start server ──────────────────────────────────────────────────────────────
    
    async function main() {
Behavior2/5

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

Annotations are absent, so description carries full burden. While 'Get' implies read-only, description fails to disclose idempotency, caching behavior, rate limits, or error conditions (e.g., what happens if unauthenticated).

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 (7 words), front-loaded action verb, zero redundancy or filler. Every word earns its place.

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?

No output schema exists, so description must compensate. It lists returned fields ('tier, limits, usage stats') but omits data structure/format, pagination, or nullability. Adequate for a 0-param tool but leaves return value shape underspecified.

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 zero parameters. Per scoring rules, 0-params baseline is 4. Description appropriately requires no parameter explanation.

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?

Clear verb ('Get') + resource ('account information') and specifies returned fields ('tier, limits, and usage stats'). Implicitly distinguishes from email-focused siblings (inbox/email tools) by targeting account metadata.

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 explicit guidance on when to invoke this tool. Does not state prerequisites (e.g., 'call this to check limits before sending') or relationship to sibling operations despite clear functional separation from email tools.

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