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

  • Handler function for the 'get_smime_info' tool. It uses the shared handleTool wrapper to authenticate and call the Gmail API method gmail.users.settings.sendAs.smimeInfo.get to retrieve the S/MIME configuration for the specified sendAsEmail and id.
      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)
        })
      }
    )
  • Zod input schema validation for the 'get_smime_info' tool, requiring 'sendAsEmail' (string) and 'id' (string).
    {
      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")
    },
  • src/index.ts:1233-1245 (registration)
    MCP server tool registration for 'get_smime_info', including name, description, input schema, and handler function.
    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)
        })
      }
    )
  • Shared helper function 'handleTool' used by get_smime_info and other tools for OAuth2 authentication, credential validation, Gmail client creation, and API call 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}`
      }
    }
  • Shared helper 'formatResponse' used to format API responses into MCP content format (JSON stringified).
    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 this is a read operation ('Gets'), but doesn't mention authentication requirements, rate limits, error conditions, or what happens if the specified config doesn't exist. For a retrieval tool with zero annotation coverage, this leaves significant behavioral gaps.

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 gets straight to the point with zero wasted words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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 2-parameter retrieval tool with no annotations and no output schema, the description provides basic purpose but lacks important context. It doesn't explain what information is returned, error handling, or how this differs from related S/MIME tools. The completeness is adequate but has clear gaps for effective agent use.

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 schema description coverage is 100%, with both parameters ('sendAsEmail' and 'id') fully documented in the input schema. The description doesn't add any additional parameter context beyond what's already in the structured data, so it meets the baseline for high schema coverage.

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 action ('Gets') and the resource ('S/MIME config for the specified send-as alias'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_smime_info' or 'set_default_smime_info', which would require more specific scope clarification.

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?

The description provides no guidance on when to use this tool versus alternatives like 'list_smime_info' or 'set_default_smime_info'. It doesn't mention prerequisites, such as needing an existing S/MIME configuration, or contextual constraints for retrieval.

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/nk900600/gmail-mcp'

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