Multi Mail

Read the signature

settings_send_as_get

Read-only

Read the signature of the address the mailbox sends from by default, as HTML, with that address. It goes under the words of every message composed from that address, unless the call passes sign false or the person has said the mailbox's company adds its own on its server. A mailbox with no signature answers without one. For an Outlook mailbox, or one whose provider is imap, it is the one Lumman keeps for it, which settings_send_as_patch sets, naming the pictures it shows without their bytes, beside the name a mailbox whose provider is imap sends under.

Input Schema

Name	Required	Description	Default
`mailbox`	Yes	The mailbox's name or its email address.

Output Schema

Name	Required	Description
`pictures`	No	The pictures the signature shows by content id, as cid:<id> in its markup, without their bytes.
`signature`	No
`displayName`	No	For a mailbox whose provider is imap, the name its mail goes out under beside its address.
`sendAsEmail`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties / displayName

Added value: +{
+  "description": "For a mailbox whose provider is imap, the name its mail goes out under beside its address.",
+  "type": "string"
+}

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties / pictures

Added value: +{
+  "description": "The pictures the signature shows by content id, as cid:<id> in its markup, without their bytes.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "mimeType": {
+        "type": "string"
+      },
+      "size": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "id",
+      "mimeType",
+      "size"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed2 schema fields changedOct 8, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedOct 5, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already establish readOnlyHint, destructiveHint false and openWorldHint false, so the description's added value is in the edge-case behavior: an empty signature returns without one, the company may append its own server-side, and inline images are named without their bytes. That is genuine context beyond the structured fields, though the final sentence is hard enough to parse that some of the value is lost.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core fact is buried in a long run-on sentence, and the trailing sentence about Outlook/imap providers is a tangled pile of relative clauses that takes several reads to decode. It is not front-loaded: the actionable read semantics are interleaved with caveats and provider minutiae.

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?

With an output schema present and annotations covering the safety profile, the description only needed to convey scoping and edge cases, which it largely does. The dangling 'sign false' reference and the impenetrable provider sentence are the only real gaps for an agent deciding whether to call it.

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

Parameters3/5

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

There is a single parameter at 100% schema description coverage ('The mailbox's name or its email address'), so the schema already does the work. The description refers to 'the mailbox' but adds no accepted forms, defaults, or resolution behavior beyond the schema. Baseline 3 applies.

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 opening clause states a specific verb and resource: read the default send-as address's signature, returned as HTML. It also names the counterpart setter, settings_send_as_patch, so the agent can place it in the read/write pair. However, the second sentence drifts into provider-specific trivia that muddies rather than sharpens the distinction from settings_send_as_find.

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 read/write pairing with settings_send_as_patch, and the description notes when a signature will be absent (no signature configured, or the company appends one server-side). There is no explicit 'use this when you need X, use the sibling when Y' statement, and the reference to a 'sign false' flag on 'the call' is ambiguous and does not correspond to any parameter in this tool's schema.

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

All Multi Mail 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.