Skip to main content
Glama
jahfer

JMAP MCP Server

by jahfer

get_mailboxes

Retrieve mailbox information from a JMAP server to manage email organization and access folders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputSchemaYes

Implementation Reference

  • index.js:69-79 (handler)
    The handler function that executes the get_mailboxes tool logic: fetches the JMAP session, extracts the mail account ID, retrieves all mailboxes via jam.api.Mailbox.get, and returns a formatted content response with JSON-stringified mailboxes.
    async () => {
      const session = await jam.session;
      const accountId = session.primaryAccounts["urn:ietf:params:jmap:mail"];
      const [mailboxes] = await jam.api.Mailbox.get({ accountId });
      return {
        content: [{
          type: "text",
          text: JSON.stringify(mailboxes, null, 2)
        }]
      };
    }
  • The input schema for the get_mailboxes tool, defined as an empty Zod object schema since no input parameters are required.
    inputSchema: z.object({}), // No input parameters needed for this tool
  • index.js:63-80 (registration)
    The server.tool call that registers the get_mailboxes tool, including its name, description, input schema, and handler function.
    server.tool(
      "get_mailboxes",
      {
        description: "Retrieves all mailboxes for the authenticated JMAP account.",
        inputSchema: z.object({}), // No input parameters needed for this tool
      },
      async () => {
        const session = await jam.session;
        const accountId = session.primaryAccounts["urn:ietf:params:jmap:mail"];
        const [mailboxes] = await jam.api.Mailbox.get({ accountId });
        return {
          content: [{
            type: "text",
            text: JSON.stringify(mailboxes, null, 2)
          }]
        };
      }
    );
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/jahfer/jmap-mcp-server'

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