Skip to main content
Glama

get_delegate

Retrieve a specific delegate's information from your Gmail account to manage email access permissions and delegation settings.

Instructions

Gets the specified delegate

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
delegateEmailYesThe email address of the delegate to retrieve

Implementation Reference

  • Registration and inline handler for the 'get_delegate' tool. The handler authenticates via handleTool, calls the Gmail API to retrieve the specified delegate, and formats the response.
    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)
        })
      }
    )
  • Input schema for the get_delegate tool, defining the required 'delegateEmail' parameter.
    {
      delegateEmail: z.string().describe("The email address of the delegate to retrieve")
    },
  • Shared helper function 'handleTool' used by get_delegate (and all tools) for OAuth2 authentication, credential validation, Gmail client creation, and error handling.
    const handleTool = async (queryConfig: Record<string, any> | undefined, apiCall: (gmail: gmail_v1.Gmail) => Promise<any>) => {
      try {
        const oauth2Client = queryConfig ? createOAuth2Client(queryConfig) : defaultOAuth2Client
        if (!oauth2Client) throw new Error('OAuth2 client could not be created, please check your credentials')
    
        const credentialsAreValid = await validateCredentials(oauth2Client)
        if (!credentialsAreValid) throw new Error('OAuth2 credentials are invalid, please re-authenticate')
    
        const gmailClient = queryConfig ? google.gmail({ version: 'v1', auth: oauth2Client }) : defaultGmailClient
        if (!gmailClient) throw new Error('Gmail client could not be created, please check your credentials')
    
        const result = await apiCall(gmailClient)
        return result
      } catch (error: any) {
        return `Tool execution failed: ${error.message}`
      }
    }
  • Helper function 'formatResponse' used to format the API response into MCP content format.
    const formatResponse = (response: any) => ({ content: [{ type: "text", text: JSON.stringify(response) }] })
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action 'gets' without detailing whether this is a read-only operation, what data is returned, error conditions, or authentication needs. For a tool with no annotation coverage, this is insufficient, as it omits critical behavioral traits like response format or access requirements.

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?

The description is extremely concise with a single sentence, 'Gets the specified delegate', which is front-loaded and wastes no words. However, it is overly brief to the point of under-specification, slightly reducing its effectiveness, but it remains structurally sound without unnecessary elaboration.

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 tool's complexity (a read operation with one parameter) and lack of annotations and output schema, the description is incomplete. It fails to explain what a delegate is, what data is returned, or any behavioral context, making it inadequate for an agent to understand the tool's full purpose and usage in the context of sibling tools like 'list_delegates'.

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?

The description adds no parameter semantics beyond what the input schema provides. The schema has 100% description coverage, with 'delegateEmail' clearly documented as 'The email address of the delegate to retrieve'. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description does not compensate but also does not detract from the schema's clarity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Gets the specified delegate' is a tautology that restates the tool name 'get_delegate' without adding meaningful context. It specifies the verb 'gets' and resource 'delegate', but lacks specificity about what a delegate is or what information is retrieved, making it vague compared to more detailed sibling tools like 'get_profile' or 'get_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 Guidelines1/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. It does not mention sibling tools like 'list_delegates' for listing all delegates or 'remove_delegate' for deletion, nor does it specify prerequisites such as needing delegate permissions or when retrieval might fail, leaving the agent without 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/HitmanLy007/gmail-mcp'

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