Skip to main content
Glama
nk900600

Gmail MCP Server

by nk900600
OverviewSchemaRelated ServersScoreDiscussions
Hybrid

list_smime_info

Retrieve S/MIME encryption configurations for a specific Gmail send-as email alias to manage secure email settings.

Instructions

Lists S/MIME configs for the specified send-as alias

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sendAsEmailYesThe email address that appears in the 'From:' header

Implementation Reference

  • src/index.ts:1262-1273 (handler)
    Registration and inline handler function for the 'list_smime_info' tool. It validates input with Zod schema requiring 'sendAsEmail', then uses handleTool to call the Gmail API gmail.users.settings.sendAs.smimeInfo.list to retrieve S/MIME configurations for the specified send-as alias.
    server.tool("list_smime_info",
  "Lists S/MIME configs for the specified send-as alias",
  {
    sendAsEmail: z.string().describe("The email address that appears in the 'From:' header")
  },
  async (params) => {
    return handleTool(config, async (gmail: gmail_v1.Gmail) => {
      const { data } = await gmail.users.settings.sendAs.smimeInfo.list({ userId: 'me', sendAsEmail: params.sendAsEmail })
      return formatResponse(data)
    })
  }
)

Tool Definition Quality

B3.1/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 it 'Lists S/MIME configs,' implying a read-only operation, but doesn't specify if it returns all configs, paginated results, error conditions, or authentication requirements. For a 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 directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and resource, making it easy to parse quickly, which is ideal for conciseness.

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 the tool has no annotations, no output schema, and a simple parameter set with full schema coverage, the description is minimally adequate. It clarifies the tool's purpose but lacks details on behavior, output format, and usage context, which are needed for full completeness in this environment.

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 input schema has 100% description coverage, with the single parameter 'sendAsEmail' clearly documented as 'The email address that appears in the 'From:' header.' The description adds no additional parameter details beyond what the schema provides, so it meets the baseline score of 3 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 ('Lists') and resource ('S/MIME configs') with specific scope ('for the specified send-as alias'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'get_smime_info' or 'insert_smime_info', which would require more specific comparison to achieve a score of 5.

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 'get_smime_info' (which might retrieve a single config) or 'insert_smime_info' (for creating configs). It lacks context on prerequisites, such as whether the send-as alias must exist or have permissions set up, leaving usage unclear.

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