Skip to main content
Glama

Hail Communication for AI

List email domains

list_email_domains
Read-onlyIdempotent

List the workspace's sending identities and default sender address.

    Returns ``items``, ``next_cursor`` and ``default_from``.
    Only identities with ``verification_status="verified"`` can send.
    For ``kind="custom"``, ``domain`` is a domain supporting any local part.
    For ``kind="hail_mail"``, it is already a complete email address.
    One verified custom domain takes priority over the Hail mail address.
    With several verified custom domains, ``default_from`` is null and email sending requires an explicit sender.
    A custom domain with ``sends_enabled`` false cannot send: it is skipped for picks and refuses an explicit ``from_``.
    Toggle it with PATCH ``/v1/email-domains/{id}`` (custom domains only).
    

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_email_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many items one page holds. ``next_cursor`` in the response points to the next page. Omitted: the API returns 50.
cursorNoPagination cursor: the ``next_cursor`` from the previous page. Omitted: the first page.
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Number of items per page. Omitted: 50."New value: +"How many items one page holds. ``next_cursor`` in the response points to the next page. Omitted: the API returns 50."
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Model ID of the calling agent. Optional. Recorded for analytics only.",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / limit / anyOf
      Previous value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maximum": 200,
      +    "minimum": 1,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / limit / description
      Previous value: -"Page size, 1 to 200. Omitted: 50."New value: +"Number of items per page. Omitted: 50."
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, yet the description adds substantial context beyond them: the returned fields, that only verified identities can send, the custom vs hail_mail distinction, priority rules among verified domains, the null default_from case, and that sends_enabled=false domains are skipped and refuse explicit from_. It stops short of describing rate limits or error behavior, but this is well above the annotation baseline.

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?

Purpose is front-loaded in the first sentence, followed by return shape and then the semantic rules in a logical order. Each line carries information, though the trailing PATCH /v1/email-domains/{id} mutation note is tangential to a read-only listing tool and adds length without aiding invocation.

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 read-only paginated list with an output schema and fully described parameters, the description covers scope, interpretation semantics, and edge cases (null default_from, disabled custom domains). Only minor gaps remain, such as pagination behavior and what happens with zero identities.

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%, so limit, cursor and llm_model are already fully documented. The description adds no parameter-level detail beyond the schema, which is the expected baseline when the schema does the work.

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?

Opens with a concrete verb+resource: 'List the workspace's sending identities and default sender address.' An agent immediately knows this enumerates sending domains/identities. It does not explicitly differentiate from siblings (e.g., route_email_domain), but the resource is specific enough that confusion is unlikely.

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 'List the workspace's ...' but there is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. The bulk of the text guides interpretation of results rather than tool selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources