Skip to main content
Glama

get_auto_forwarding

Retrieve your Gmail auto-forwarding configuration to see the forwarding address and its status.

Instructions

Gets auto-forwarding settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:831-840 (registration)
    Registration of the 'get_auto_forwarding' tool on the MCP server using server.tool() with name 'get_auto_forwarding' and description 'Gets auto-forwarding settings'. No input parameters required (empty schema).
    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)
        })
      }
    )
  • Handler function that executes the tool logic. Calls gmail.users.settings.getAutoForwarding({ userId: 'me' }) via the Gmail API to retrieve auto-forwarding settings, and returns the formatted response.
      async () => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.settings.getAutoForwarding({ userId: 'me' })
          return formatResponse(data)
        })
      }
    )
  • Input schema for get_auto_forwarding - empty object ({}) since the tool takes no parameters.
    {},
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only states the basic action. It does not confirm that the operation is read-only, mention any permissions, or describe side effects, leaving the agent with minimal insight.

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?

A single short sentence conveys the purpose without any extra words. It is perfectly concise and front-loaded.

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?

Given no output schema and no parameters, the description is minimal. While it is functional, it could be improved by hinting at the structure or common fields of the auto-forwarding settings, but it meets the minimum for a simple getter.

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 zero parameters, so schema coverage is trivially 100%. The description adds no further meaning, but as per calibration guidelines, 0 parameters gives a baseline of 4.

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?

The description 'Gets auto-forwarding settings' clearly states the action (gets) and the resource (auto-forwarding settings), distinguishing it from siblings like update_auto_forwarding.

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 is provided on when to use this tool versus alternatives such as get_forwarding_address or update_auto_forwarding. The description lacks context for choosing this tool over siblings.

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