MCP Aruba Email & Calendar Server

Overview Schema Source Related Servers Discussions Admin

set_email_signature

Creates and saves an email signature with optional photo and colors, automatically appending it to all sent emails; generates an HTML signature when photo or color is provided.

Instructions

Create and save a professional email signature with optional photo and colors.

The signature will be automatically appended to all sent emails. If photo_url or color are provided, an HTML signature will be created.

Args: name: Full name (e.g., "Giacomo Fiorucci") email: Email address role: Job title/role (optional, e.g., "Software Developer") company: Company name (optional, e.g., "Emotion Team") phone: Phone number (optional, e.g., "+39 123 456 7890") photo_url: URL or local file path to profile photo (optional, auto-uploads if local file) color: Hex color code for accents (optional, e.g., "#0066cc", "#FF5722") style: Signature style - "professional", "minimal", "colorful" (default: "professional") signature_name: Name to save signature as (default: "default")

Returns: Confirmation with signature preview

Examples: # Simple text signature set_email_signature( name="Giacomo Fiorucci", email="giacomo.fiorucci@emotion-team.com", role="Software Developer", company="Emotion Team" )

# HTML signature with photo and custom color
set_email_signature(
    name="Giacomo Fiorucci",
    email="giacomo.fiorucci@emotion-team.com",
    role="Software Developer",
    company="Emotion Team",
    phone="+39 123 456 7890",
    photo_url="https://example.com/photo.jpg",
    color="#0066cc",
    style="professional"
)

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>",
      "email": "<email>"
    },
    "name": "set_email_signature"
  }
}

Input Schema

Name	Required	Default
`name`	Yes
`role`	No
`color`	No
`email`	Yes
`phone`	No
`style`	No	professional
`company`	No
`photo_url`	No
`signature_name`	No	default

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Nov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the global side effect that the signature is appended to all sent emails, that local photo paths are auto-uploaded, and that a preview is returned. It does not say whether saving under an existing signature_name overwrites it, which is the main remaining behavioral gap.

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 prose preamble is front-loaded and efficient, but the Args block and the two Examples largely restate the same information, making the definition longer than needed. Structure is clear, yet the duplication costs it points on conciseness.

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 nine-parameter mutation tool with no annotations, the description covers parameters, side effects, and conditional HTML generation, and an output schema exists so return values need not be explained. The only meaningful omission is overwrite/conflict behavior for signature_name and any permission requirements.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate, and it does: all nine parameters are documented with meaning, optionality, defaults, and concrete formats (hex color examples, URL-or-local-path for photo_url, style default 'professional', signature_name default 'default'). This adds substantial meaning beyond the bare schema titles.

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?

The description opens with a specific verb and resource: 'Create and save a professional email signature'. It is clearly distinguishable from the read-side siblings get_email_signature and list_email_signatures, though it never names them explicitly.

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?

It states the key effect ('automatically appended to all sent emails') and the conditional behavior ('If photo_url or color are provided, an HTML signature will be created'), which implies when the tool is relevant. However, it gives no explicit when-to-use vs. when-not guidance and never points to get_email_signature or list_email_signatures as the way to inspect existing signatures.

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