Skip to main content
Glama

list_sender_addresses

Read-only

Lists available sender addresses and display names so you can choose the correct from address when sending email; the first address is the default.

Instructions

List the addresses send_email can send from, with the display name used for each.

The first one is the default for new emails; replies default to the address the original email was sent to. Pass one as send_email's from_address.

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": "list_sender_addresses"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safe-read profile is covered. The description adds genuinely non-obvious behavior beyond that: ordering matters because the first entry is the default, and the reply-default rule differs from the new-email default. It doesn't say whether the list can be empty or whether it's scoped per account, which keeps it from a 5.

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

Conciseness5/5

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

Three short sentences, front-loaded with what is listed, followed by the ordering/default rules and the integration hint. No sentence is filler, and the most decision-relevant facts (what it lists, default position) come first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a parameterless read tool with an output schema and explicit read-only annotations, so return-format documentation is not the description's burden. What remains — what the list contains, its ordering semantics, and how to consume an entry — is fully covered.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description wisely spends its words on what the returned entries mean rather than inventing parameter detail.

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 description opens with a specific verb and resource: "List the addresses send_email can send from," and adds the scope detail that each entry carries its display name. That is enough for an agent to distinguish this from send_email, list_emails, or search_emails 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 Guidelines4/5

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

It gives explicit downstream usage: "Pass one as send_email's from_address," which tells the agent exactly why and when to call this tool. It also resolves selection semantics (first entry is the default for new mail, replies default to the original recipient). It stops short of stating any exclusions or edge cases, but no real alternative tool exists for this lookup.

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