Skip to main content
Glama

List sending domains

domain_list
Read-onlyIdempotent

Lists the sending domain and its status (pending, verified or failed) with each DNS record and whether it was found. Free and read only. Check this before drafting: a workspace that must send from its own domain cannot schedule until it is verified. Requires API key scope: read.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, yet the description still adds material facts: the call is free (no quota/cost) and requires API key scope 'read'. It also discloses the shape of what comes back, including per-record found/not-found status, which the annotations cannot convey.

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, each doing distinct work: what is returned, cost/safety, and the scheduling gate. The most decision-relevant content (the verification gate) is front-loaded before drafting context, with no filler.

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 no output schema, the description usefully compensates by describing the return payload and the auth requirement. The one residual ambiguity is whether the response contains one domain or many — 'Lists the sending domain' is singular while 'each DNS record' implies a collection, which matters for an agent parsing the result.

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 the baseline is 4 and there is nothing for the description to disambiguate. No misleading parameter language is introduced.

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?

States a specific verb and resource (lists the sending domain) and enumerates the returned fields: status in {pending, verified, failed}, each DNS record, and whether each record was found. That detail lets an agent distinguish it from sibling mutations like domain_add, domain_remove, and domain_verify 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?

Gives an explicit pre-condition workflow: check this before drafting, because a workspace sending from its own domain cannot schedule until verified. That is strong when-to-use guidance, but it never names the natural follow-up alternative (domain_verify) for actually fixing a pending or failed status, so the routing is only half complete.

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