Skip to main content
Glama
Purelymail MCP

Purelymail MCP

by amplia-labs

List domains

list_domains
Read-only

Lists domains available to the account with settings and DNS summary (MX, SPF, DKIM, DMARC); optionally includes Purelymail shared domains.

Instructions

Lists domains accessible to the account, with their settings and a DNS summary (MX, SPF, DKIM, DMARC).

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

Input Schema

NameRequiredDescriptionDefault
includeSharedNoWhether to include Purelymail shared domains. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description earns credit beyond that by disclosing the shape of the result (per-domain settings and a DNS record summary), which matters because there is no output schema. It omits pagination, rate limits, or result-size behavior.

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?

A single front-loaded sentence covering verb, scope, and return contents with zero filler. Nothing is padded or repeated.

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?

A read-only, zero-required-parameter listing tool with no output schema is well served by a description that names the returned fields. The remaining gap is whether the result is paginated or size-bounded and how includeShared changes the set.

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?

Only one optional parameter (includeShared) and the schema documents it at 100% coverage, so the baseline is 3. The phrase "accessible to the account" loosely gestures at shared-domain scope but never names or explains the flag, so no real meaning is added.

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?

States a specific verb and resource ("Lists domains accessible to the account") and adds the returned payload (settings plus an MX/SPF/DKIM/DMARC DNS summary). That clearly separates it from add_domain, delete_domain and update_domain_settings, though no sibling is named explicitly.

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 only implied: an agent can infer this is the discovery call before update_domain_settings or delete_domain, but the description never says when to call it, when not to, or what other listing tools exist. No exclusions or prerequisites are stated.

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