Skip to main content
Glama
Sign In
multi-gmail-mcp

multi-gmail-mcp

by japan08
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Set the name signed on reply drafts

set_signer

Sets your signer display name and optional follow-up label for Gmail replies in the current session.

Instructions

Saves the display name used on reply drafts for this session, and optionally the Gmail follow-up label name. Call after login when the user says how they want to sign. Advanced: chatScope / accountAlias only if README multi-account or shared-session section applies.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "set_signer"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
followUpLabelNo
accountAliasNo
chatScopeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It lacks details on side effects (e.g., overwrites previous signer), persistence scope, error handling, or authentication requirements beyond login timing.

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?

Four sentences, each serving a purpose: core function, timing, advanced usage. No redundant text, but could be more streamlined by integrating the advanced note into the first sentence.

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?

Covers the main purpose and parameter semantics, but lacks information on return values, error conditions, session lifecycle, and differentiation from closely related tools like multi_gmail_set_signer, leaving gaps for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, the description compensates by explaining that 'name' is the display name, 'followUpLabel' is the Gmail follow-up label, and advanced parameters are for multi-account or shared-session, adding meaning beyond the schema's technical constraints.

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?

The description clearly states the tool saves the display name used on reply drafts for the session, which is a specific verb+resource combination. It distinguishes from siblings like set_draft or set_mode by focusing on signer name for replies.

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

Usage Guidelines4/5

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

Explicitly says 'Call after login when the user says how they want to sign', providing clear timing and trigger. Mentions advanced parameters for multi-account scenarios, offering some guidance, but doesn't directly contrast with sibling tools.

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