Skip to main content
Glama
shinzo-labs

Gmail MCP

by shinzo-labs
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

get_imap

Retrieve Gmail IMAP settings to configure email clients. Access IMAP server details for email synchronization.

Instructions

Gets IMAP settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:842-851 (handler)
    The 'get_imap' tool registration and handler. It's a tool that gets IMAP settings by calling gmail.users.settings.getImap(). No parameters are required. The handler wraps the call in handleTool() with formatResponse().
    server.tool("get_imap",
  "Gets IMAP settings",
  {},
  async () => {
    return handleTool(config, async (gmail: gmail_v1.Gmail) => {
      const { data } = await gmail.users.settings.getImap({ userId: 'me' })
      return formatResponse(data)
    })
  }
)
  • src/index.ts:842-843 (registration)
    Registration of the 'get_imap' tool via server.tool() with name 'get_imap' and description 'Gets IMAP settings'. No schema parameters defined (empty object {}).
    server.tool("get_imap",
  "Gets IMAP settings",

Tool Definition Quality

B3.2/5.0
Behavior3/5

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

Without annotations, the description implies a safe read operation but does not explicitly disclose side effects or permissions. Minimal transparency for a simple getter.

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

Conciseness4/5

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

Extremely concise with no wasted words, but could be slightly more descriptive without hurting brevity.

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?

Lacks information about return values, prerequisites, or what 'IMAP settings' entails. For a tool with no output schema, more context is needed.

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?

No parameters exist, so schema coverage is 100%. Baseline score of 4 applies as no additional parameter info is needed.

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 'Gets IMAP settings' clearly states the verb and resource, distinguishing it from sibling tools like update_imap and other get_* tools.

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 vs alternatives, no prerequisites or context about IMAP setup.

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/shinzo-labs/gmail-mcp'

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