Skip to main content
Glama
shinzo-labs

Gmail MCP

by shinzo-labs
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

get_send_as

Retrieve a specific send-as alias from your Gmail account. Requires the alias email address.

Instructions

Gets the specified send-as alias

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sendAsEmailYesThe send-as alias to be retrieved

Implementation Reference

  • src/index.ts:1158-1169 (registration)
    Registration of the 'get_send_as' tool via server.tool(), including its schema (sendAsEmail parameter) and the handler that calls gmail.users.settings.sendAs.get()
    server.tool("get_send_as",
  "Gets the specified send-as alias",
  {
    sendAsEmail: z.string().describe("The send-as alias to be retrieved")
  },
  async (params) => {
    return handleTool(config, async (gmail: gmail_v1.Gmail) => {
      const { data } = await gmail.users.settings.sendAs.get({ userId: 'me', sendAsEmail: params.sendAsEmail })
      return formatResponse(data)
    })
  }
)

Tool Definition Quality

A3.5/5.0
Behavior3/5

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

The description implies a read-only operation through 'Gets', but with no annotations provided, it does not disclose additional traits like required permissions or side effects. Adequate for a simple getter, but minimal.

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?

Extremely concise: one sentence of 7 words with no filler. All text is relevant to the tool's function.

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 the tool's simplicity (one required parameter, no output schema), the description is adequate but does not explain what is returned or the need for the alias to exist. Minor gaps for a complete picture.

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

Parameters3/5

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

Schema coverage is 100%, and the description adds only 'to be retrieved', which echoes the schema description. No extra meaning beyond the schema, so baseline 3.

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 the specified send-as alias' uses a specific verb (Gets) and resource (send-as alias), clearly distinguishing it from sibling tools like list_send_as or create_send_as.

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 such as list_send_as or verify_send_as. The description lacks context for tool selection.

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