Skip to main content
Glama

get_smime_info

Retrieve S/MIME encryption configuration details for a specific email alias to verify secure message settings.

Instructions

Gets the specified S/MIME config for the specified send-as alias

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sendAsEmailYesThe email address that appears in the 'From:' header
idYesThe immutable ID for the S/MIME config

Implementation Reference

  • src/index.ts:1214-1226 (registration)
    Registration of the 'get_smime_info' tool, including input schema and inline handler function. The handler uses the Gmail API to retrieve specified S/MIME configuration for a send-as alias.
    server.tool("get_smime_info",
      "Gets the specified S/MIME config for the specified send-as alias",
      {
        sendAsEmail: z.string().describe("The email address that appears in the 'From:' header"),
        id: z.string().describe("The immutable ID for the S/MIME config")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.settings.sendAs.smimeInfo.get({ userId: 'me', sendAsEmail: params.sendAsEmail, id: params.id })
          return formatResponse(data)
        })
      }
    )
  • Handler function for 'get_smime_info' tool that authenticates via handleTool, calls Gmail API gmail.users.settings.sendAs.smimeInfo.get, and formats the response.
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.settings.sendAs.smimeInfo.get({ userId: 'me', sendAsEmail: params.sendAsEmail, id: params.id })
          return formatResponse(data)
        })
      }
    )
  • Input schema for 'get_smime_info' tool using Zod: requires sendAsEmail and id.
    {
      sendAsEmail: z.string().describe("The email address that appears in the 'From:' header"),
      id: z.string().describe("The immutable ID for the S/MIME config")
    },
  • Shared helper function handleTool used by all Gmail API tools, including get_smime_info, for OAuth authentication and API execution.
    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 to format API responses into MCP content structure, used by get_smime_info handler.
    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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a read operation ('Gets'), which implies it's non-destructive and likely read-only, but doesn't specify authentication requirements, rate limits, error conditions, or what happens if the config doesn't exist. This leaves gaps for a tool that retrieves sensitive security configurations.

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 that front-loads the core purpose without unnecessary words. It directly states the action and target, making it easy to parse quickly.

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 annotations and no output schema, the description is minimal but covers the basic purpose. For a read operation with two well-documented parameters, it's adequate but lacks details on behavioral aspects like permissions or return format, which would be helpful for an AI agent to use it correctly in context.

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 description coverage is 100%, with clear descriptions for both parameters ('sendAsEmail' and 'id'). The description adds minimal value beyond the schema, as it mentions 'specified send-as alias' which aligns with 'sendAsEmail' but doesn't explain the relationship between parameters or provide additional context like format examples.

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 clearly states the verb ('Gets') and resource ('specified S/MIME config'), specifying it's for a particular send-as alias. It distinguishes from siblings like 'list_smime_info' (which lists all) and 'delete_smime_info' (which removes). However, it doesn't explicitly mention it retrieves a single config, which could be inferred but isn't stated outright.

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 like 'list_smime_info' (for listing all configs) or 'set_default_smime_info' (for setting defaults). The description implies usage for a specific config but doesn't clarify prerequisites or exclusions, such as needing existing S/MIME configurations.

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