Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

gmail.users.settings.sendAs.smimeInfo.delete

Delete an S/MIME configuration associated with a Gmail send-as alias by specifying the user, alias, and SmimeInfo ID. This removes the certificate entry from the alias.

Instructions

Deletes the specified S/MIME config for the specified send-as alias. For more information, see Manage S/MIME certificates with the Gmail API [HTTP DELETE] — removes the resource; irreversible unless the API documents a trash/undo flow; refused under --readonly safety profiles. Returns the post-delete resource state (or empty) as JSON — request bodies are built from the typed parameters (typed flags win over the params map), or read whole from body_file Siblings over the same resource: get, insert, list, setDefault.

Input Schema

NameRequiredDescriptionDefault
idYes[URL path segment] The immutable ID for the SmimeInfo.
queryNoExtra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
paramsNoParameter map merged into the request; typed parameters win.
userIdYes[URL path segment] The user's email address. The special value `me` can be used to indicate the authenticated user.me
dry_runNoReturn the request that would be sent, without sending it.
body_fileNoRead the request body from this file ('-' for stdin) instead of building one from the parameters.
sendAsEmailYes[URL path segment] The email address that appears in the "From:" header for mail sent using this alias.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"The immutable ID for the SmimeInfo."New value: +"[URL path segment] The immutable ID for the SmimeInfo."
    • changedInput schema / properties / sendAsEmail / description
      Previous value: -"The email address that appears in the \"From:\" header for mail sent using this alias."New value: +"[URL path segment] The email address that appears in the \"From:\" header for mail sent using this alias."
    • addedInput schema / properties / userId / default
      Added value: +"me"
    • changedInput schema / properties / userId / description
      Previous value: -"The user's email address. The special value `me` can be used to indicate the authenticated user."New value: +"[URL path segment] The user's email address. The special value `me` can be used to indicate the authenticated user."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it declares the operation irreversible, notes it is refused under --readonly safety profiles, and states that the post-delete resource state (or empty) is returned as JSON. The trailing text about request bodies and body_file is irrelevant noise for a bodiless DELETE.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key fact (what is deleted, irreversibility) is front-loaded, but the definition is padded with generic wrapper boilerplate about typed flags, params maps, and body_file that cannot apply to a bodyless DELETE.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but the description tells the agent what comes back (post-delete resource state or empty) and warns of irreversibility and readonly-profile refusal, which is enough to call it safely.

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 userId, sendAsEmail, and id are already documented. The description only restates the resource scoping ('specified S/MIME config', 'specified send-as alias'), adding no format or constraint detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (deletes) and a precisely scoped resource (the S/MIME config for a given send-as alias), and lists the sibling operations on the same resource (get, insert, list, setDefault), so an agent can place it immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description names sibling alternatives but never states the conditions under which an agent should delete versus use setDefault or get; usage is implied by the word 'delete' rather than explained. The linked S/MIME guide is the only outward pointer.

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