Skip to main content
Glama
HitmanLy007

Gmail MCP

by HitmanLy007
OverviewSchemaRelated ServersScoreDiscussions
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")
},

Tool Definition Quality

C2.9/5.0
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 'set' operation, implying mutation, but doesn't clarify if it overwrites existing defaults, requires specific permissions, or has side effects. This leaves critical behavioral traits unspecified for a mutation tool.

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 directly states the tool's purpose without any redundant or unnecessary information. It is appropriately sized and front-loaded, making it easy to parse quickly.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits, error conditions, or what constitutes success, leaving gaps in understanding how the tool operates in context. This is particularly problematic given the tool's potential impact on email security settings.

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%, so the input schema already fully documents the two parameters. The description adds no additional meaning beyond implying that 'sendAsEmail' is an alias and 'id' refers to an S/MIME config, which is already covered in the schema descriptions. This 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 ('Sets') and the resource ('default S/MIME config for the specified send-as alias'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'insert_smime_info' or 'delete_smime_info', which prevents a perfect score.

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 'insert_smime_info' or 'update_send_as', nor does it mention prerequisites such as existing S/MIME configurations or send-as aliases. This lack of context makes it harder for an agent to choose appropriately among siblings.

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