Skip to main content
Glama
HitmanLy007

Gmail MCP

by HitmanLy007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

set_default_smime_info

Configure the default S/MIME encryption settings for a Gmail send-as email alias to ensure secure message transmission.

Instructions

Sets the default 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:1256-1268 (registration)
    Registration of the 'set_default_smime_info' tool. Includes input schema (sendAsEmail and id), description, and inline handler function that validates OAuth credentials via handleTool and calls the Gmail API gmail.users.settings.sendAs.smimeInfo.setDefault to set the default S/MIME configuration for the specified send-as alias.
    server.tool("set_default_smime_info",
  "Sets the default 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.setDefault({ userId: 'me', sendAsEmail: params.sendAsEmail, id: params.id })
      return formatResponse(data)
    })
  }
)
  • src/index.ts:1262-1267 (handler)
    The handler function for the tool, which uses the shared handleTool utility to create/authenticate a Gmail client and invoke the setDefault method on smimeInfo for the given sendAsEmail and id.
    async (params) => {
  return handleTool(config, async (gmail: gmail_v1.Gmail) => {
    const { data } = await gmail.users.settings.sendAs.smimeInfo.setDefault({ userId: 'me', sendAsEmail: params.sendAsEmail, id: params.id })
    return formatResponse(data)
  })
}
  • src/index.ts:1258-1261 (schema)
    Zod schema defining the input parameters: 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")
},

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral traits. It fails to disclose whether the operation is idempotent, if it overrides an existing default, what happens if the config doesn't exist, or any required permissions.

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?

A single sentence that is front-loaded and efficient. However, it could incorporate additional context without becoming overly verbose, such as specifying that the config must already exist.

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?

The tool is simple with two required parameters and no output schema. The description covers the core purpose but lacks behavioral details and differentiation from siblings. It is adequate but not fully complete.

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%, defining sendAsEmail and id. The description adds no further meaning beyond the schema, which is sufficient for a baseline 3.

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 (sets) and the resource (default S/MIME config) with context (for a send-as alias). It differentiates from siblings like insert_smime_info and delete_smime_info, but does not explicitly contrast them.

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 versus alternatives like insert_smime_info or list_smime_info. The description implies setting a default, but does not specify prerequisites or scenarios where this tool is preferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools