Skip to main content
Glama
shinzo-labs

Gmail MCP

by shinzo-labs
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

get_delegate

Retrieve details of a Gmail delegate by providing their email address.

Instructions

Gets the specified delegate

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
delegateEmailYesThe email address of the delegate to retrieve

Implementation Reference

  • src/index.ts:988-999 (registration)
    Registration of the 'get_delegate' tool using server.tool().
    server.tool("get_delegate",
  "Gets the specified delegate",
  {
    delegateEmail: z.string().describe("The email address of the delegate to retrieve")
  },
  async (params) => {
    return handleTool(config, async (gmail: gmail_v1.Gmail) => {
      const { data } = await gmail.users.settings.delegates.get({ userId: 'me', delegateEmail: params.delegateEmail })
      return formatResponse(data)
    })
  }
)
  • src/index.ts:993-998 (handler)
    Handler function for the 'get_delegate' tool. Calls Gmail API's delegates.get with the provided delegateEmail and wraps the response using formatResponse.
    async (params) => {
  return handleTool(config, async (gmail: gmail_v1.Gmail) => {
    const { data } = await gmail.users.settings.delegates.get({ userId: 'me', delegateEmail: params.delegateEmail })
    return formatResponse(data)
  })
}
  • src/index.ts:990-992 (schema)
    Input schema definition for the 'get_delegate' tool. Expects a single 'delegateEmail' string parameter.
    {
  delegateEmail: z.string().describe("The email address of the delegate to retrieve")
},

Tool Definition Quality

A3.7/5.0
Behavior3/5

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

The description implies a read-only operation ('Gets'), but without annotations, it does not explicitly state behavioral traits like idempotency, auth requirements, or side effects. It is minimally adequate but not rich.

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 single sentence with no wasted words. Front-loads the action and resource efficiently.

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?

For a simple get operation with one parameter and no output schema, the description does not specify what is returned. It is adequate but could be more complete by hinting at the return value or structure.

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% with a clear parameter description in the schema. The tool description adds no extra meaning beyond what the schema already provides, 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 clearly states the action ('Gets') and the resource ('the specified delegate'), distinguishing it from siblings like list_delegates (list all) and remove_delegate (delete).

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

Usage Guidelines3/5

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

No explicit guidance on when to use or when not to use. The purpose is implied by the parameter (delegateEmail) and sibling context, but the description lacks explicit alternatives or exclusions.

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