Argorant

Set the signature of many mailboxes

argorant_set_inbox_signatures

Destructive

Give many mailboxes the same signature text in one call, chosen by address, domain, tag, order or all=true; the sender variables make each mailbox sign with its own name. Use it for bulk changes; for one mailbox use argorant_set_inbox_signature and for the workspace default argorant_set_default_signature. Only the fields you pass change, and clear=true removes their own signatures so they use the default. A signature only appears where an email or reply contains {{signature}}, in the first email and follow-ups alike; without it nothing is added, except that replies from an agent sign on their own. Links need format html with simple HTML. replies_only is no longer used. More in the docs at https://docs.argorant.com/docs/agents/tools#analytics-mailbox-settings-blocklist

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description
`all`	No	true for every mailbox in the workspace
`tags`	No	Mailboxes that carry all of these tags.
`clear`	No	true removes their own signatures
`title`	No	A job title to use for {{sender_title}}.
`emails`	No	Mailbox addresses.
`format`	No	text (default) or html
`company`	No	A company name to use for {{sender_company}}.
`domains`	No	Every mailbox on these domains.
`order_id`	No	Every mailbox this order created.
`template`	No	The signature, fixed text with the variables {{sender_first_name}}, {{sender_last_name}}, {{sender_full_name}}, {{sender_title}}, {{sender_company}} and {{sender_email}}, for example "Best,\n{{sender_first_name}} {{sender_last_name}}\n{{sender_title}}, {{sender_company}}". No {a\|b} variations.
`replies_only`	No	No longer used. Still accepted so older clients keep working, but it changes nothing.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The annotations already declare a non-read-only, destructive, closed-world mutation, and the description adds real behavior on top: partial-update semantics (only passed fields change), that clear=true reverts mailboxes to the default, and the crucial rendering condition that a signature only appears where content contains {{signature}}. It also flags that links require format html and that replies_only is a deprecated no-op. The one murky clause about replies from an agent signing on their own slightly blurs the rule it just stated.

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 important scoping and sibling routing is front-loaded, but the middle sentence about {{signature}} rendering, follow-ups and agent replies sprawls into a dense run-on that is hard to parse on first read. A split into short sentences or bullets would keep all the information while making it scannable.

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 an 11-parameter bulk mutation with an output schema and destructive annotations, the description covers selection, partial updates, clearing, rendering prerequisites and a deprecated parameter, plus a docs link. What is missing is a stated default when no selector is provided and any note on scale or batching limits for very large selections.

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?

Schema coverage is 100%, so the baseline is 3. The description earns above that by explaining the intent behind parameters the schema documents only mechanically: the sender variables make each mailbox sign with its own name, format html is what links need, and replies_only is accepted but inert. It does not explain what happens when no selector at all is supplied, which is the main remaining ambiguity across 11 optional parameters.

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 opening clause gives a specific verb, resource and scope: give many mailboxes the same signature text in one call. It then names the two closest siblings, argorant_set_inbox_signature for a single mailbox and argorant_set_default_signature for the workspace default, so an agent can pick it out without opening any schema.

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

Usage Guidelines5/5

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

Explicit routing rules are given: bulk changes here, one mailbox to argorant_set_inbox_signature, workspace default to argorant_set_default_signature. It also states the selection axes (address, domain, tag, order, all=true) and the clear=true alternative, so when-to-use is fully covered.

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

All Argorant tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.