Skip to main content
Glama
mail-mcp-server

mail-mcp-server

list_send_as

List the send-as addresses available for a connected mailbox, including display names, default status, verification state, and signatures.

Instructions

The addresses the mailbox can send as, with display names, default, verification and signatures.

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": {
      "mailbox": "<mailbox>"
    },
    "name": "list_send_as"
  }
}

Input Schema

NameRequiredDescriptionDefault
mailboxYesA connected mailbox address (see list_mailboxes)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the returned attributes (display names, default flag, verification status, signatures), which is useful, but says nothing about permissions needed, whether the list is paginated or empty for unconfigured mailboxes, or whether it touches any external state.

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?

One short sentence with no wasted wording, and the returned fields are enumerated compactly. The only flaw is the missing verb, which makes the opening slightly ungrammatical.

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 simple read-only, single-parameter listing tool with no output schema, enumerating the returned fields (display names, default, verification, signatures) covers what an agent needs to decide whether to call it. Minor gaps around ordering and empty results are tolerable at this complexity.

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?

Schema description coverage is 100% and the single mailbox parameter is documented in the schema, including a pointer to list_mailboxes. The description adds no additional meaning about the parameter (e.g., format or accepted aliases), so the baseline of 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?

Despite the missing verb ("The addresses the mailbox can send as"), the description clearly identifies the resource: send-as addresses belonging to a given mailbox. An agent can distinguish it from the plan_*_send_as siblings, which by name imply mutation planning rather than listing.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no mention of related siblings such as plan_create_send_as or plan_delete_send_as, and no stated prerequisites. The only implied usage comes from the tool name and the read-only nature of a list operation.

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