Skip to main content
Glama

ProSignature email signatures

Install steps for a mail client

get_install_steps
Read-onlyIdempotent

How to add, change or install an email signature in a mail client, honestly: Gmail web (paste, or the sendAs PATCH with gmail.settings.basic — new mail only), Gmail mobile, Outlook (copy-paste only, no directory sync), Apple Mail, iPhone, and google_workspace (the one-time super-admin approval: client ID, scopes, admin console path). The free Chrome extension (auto-updates, covers replies) needs the human to sign up first.

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": {
      "client": "<client>"
    },
    "name": "get_install_steps"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientYesWhich mail client

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / client / enum
      Previous value: -[
      -  "gmail",
      -  "gmail_mobile",
      -  "outlook",
      -  "apple_mail",
      -  "iphone"
      -]New value: +[
      +  "gmail",
      +  "gmail_mobile",
      +  "outlook",
      +  "apple_mail",
      +  "iphone",
      +  "google_workspace"
      +]
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that — OAuth scope requirements, the 'new mail only' limitation of the sendAs route, and the fact that the Chrome extension requires a human signup — but it never says what the response contains (steps text? links?) or how the guidance is scoped.

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?

It is one long run-on sentence with nested parentheticals and an editorial aside ('honestly:'), which makes it dense to parse. The purpose is front-loaded, but the client-by-client caveats would read far better as a short list.

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?

For a read-only, single-enum-parameter tool with no output schema, the description covers the important ground: which clients, per-client constraints, admin prerequisites, and the extension caveat. The main remaining gap is that it never characterizes the return value, which matters since no output schema exists to fill that in.

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?

The schema already names the six enum values at 100% coverage, but the description adds meaning the enum cannot: Outlook is copy-paste only with no directory sync, google_workspace requires one-time super-admin approval with client ID and scopes, Gmail web supports sendAs PATCH with gmail.settings.basic. That materially changes which value an agent should choose.

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?

States a specific verb and resource ('How to add, change or install an email signature in a mail client') and enumerates the covered clients, so an agent knows exactly what comes back. It does not, however, distinguish itself from the sibling get_signature_playbook, which sounds like it could cover adjacent ground.

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?

Usage is implied by the client enumeration and by per-client caveats ('Gmail web ... new mail only', 'Outlook copy-paste only'), which help an agent pick the right enum value. There is no explicit when-to-use/when-not statement or routing to the sibling tools, so the guidance is contextual rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.