Skip to main content
Glama
nk900600

Gmail MCP Server

by nk900600
OverviewSchemaRelated ServersScoreDiscussions
Hybrid

get_auto_forwarding

Retrieve auto-forwarding configuration from Gmail to view or verify email forwarding rules and settings.

Instructions

Gets auto-forwarding settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:817-826 (handler)
    The handler and registration for the 'get_auto_forwarding' tool. It calls the Gmail API to get auto-forwarding settings and formats the response.
    server.tool("get_auto_forwarding",
  "Gets auto-forwarding settings",
  {},
  async () => {
    return handleTool(config, async (gmail: gmail_v1.Gmail) => {
      const { data } = await gmail.users.settings.getAutoForwarding({ userId: 'me' })
      return formatResponse(data)
    })
  }
)

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the action ('Gets') without mentioning permissions required, rate limits, response format, or whether it's read-only. This leaves significant gaps in understanding how the tool behaves, warranting a score of 2.

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 ('Gets auto-forwarding settings') that directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, earning the highest score for conciseness.

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. It does not explain what the tool returns (e.g., settings details) or any behavioral aspects like error conditions. For a tool with no structured data support, this minimal description is inadequate, resulting in a low score.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add parameter information, which is appropriate, resulting in a baseline score of 4 as it does not need to compensate for any schema gaps.

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 auto-forwarding settings' clearly states the verb ('Gets') and resource ('auto-forwarding settings'), making the purpose unambiguous. However, it does not differentiate from sibling tools like 'get_forwarding_address' or 'update_auto_forwarding', which limits its score to 4 instead of 5.

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. For example, it does not specify if this is for retrieving current settings before using 'update_auto_forwarding' or how it differs from 'get_forwarding_address'. This lack of contextual usage information results in a low score.

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

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