Argorant

Set the default signature

argorant_set_default_signature

Destructive

Set the workspace default signature, used by every mailbox without its own, or remove it with clear=true. Use it for the default; for one mailbox use argorant_set_inbox_signature and for many argorant_set_inbox_signatures. 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_default_signature"
  }
}

Input Schema

Name	Required	Description
`clear`	No	true removes the default signature
`title`	No	A job title to use for {{sender_title}}.
`format`	No	text (default) or html
`company`	No	A company name to use for {{sender_company}}.
`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.
`workspace`	No	For team accounts only: a workspace number.
`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.7/5.0

Behavior5/5

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

Annotations only say this is a non-read-only, destructive mutation. The description adds real behavioral context beyond them: the signature is only injected where the email contains the {{signature}} placeholder, nothing is added otherwise, agent-sent replies self-sign, links require format=html with simple HTML, and replies_only is a no-op retained for compatibility. That is substantive disclosure of effects and side conditions the annotations cannot express.

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?

The mutation/removal action and the sibling routing are front-loaded, and most sentences carry non-obvious information (placeholder behavior, deprecation). It is on the dense side, with the docs URL and the agent-reply caveat adding length that is only marginally load-bearing.

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 destructive, zero-required-parameter mutation with an output schema, the description covers scope, alternatives, placeholder semantics and removal. The one remaining ambiguity is what a call with no arguments at all does (no template provided, clear not set), which is not addressed.

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 description coverage is already 100%, so the baseline is 3, but the description adds meaning on top: it restates clear=true as removal, constrains html formatting to 'simple HTML' for links, and flags replies_only as deprecated and inert. It does not explain the interaction of title/company with the template placeholders beyond what the schema says.

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 and resource ('Set the workspace default signature') plus the removal variant ('remove it with clear=true'), and immediately scopes it as applying to 'every mailbox without its own'. That scope statement is exactly what separates it from argorant_set_inbox_signature and argorant_set_inbox_signatures.

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 is given: 'Use it for the default; for one mailbox use argorant_set_inbox_signature and for many argorant_set_inbox_signatures.' The when-to-use decision is fully resolved and the alternatives are named by exact tool.

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.