Skip to main content
Glama

Check my owner's sending domain setup

check_sender
Destructive

Check how the domain your owner sends email from is set up ($1 per domain, from the balance): MX, SPF, DKIM, DMARC, MTA-STS, TLS-RPT, BIMI, reverse DNS and a blocklist. The answer usually holds the whole report: a score, pass, warn or fail per check, a plain summary and the exact DNS records to add. Reading one again is free: get_sender_check or list_sender_checks. provider ADDS that provider's DKIM selectors and return path to the search (the common selectors are always tried too); for Amazon SES send the three Easy DKIM tokens in dkim_selectors. A bigger order waits for your owner's approval (pending_approval). Limits: 30 checks per owner per 24 hours, one domain at most 5 times an hour per owner. Public DNS only; nothing is sent. This report checks your DNS setup only. Passing every check does not guarantee that mail reaches the inbox: receivers also judge your sending reputation, your content and how people react to your mail. More: /llms/sender-health-check.md.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "example.com",
      "idempotency_key": "example-check-1",
      "max_price_cents": 100
    },
    "name": "check_sender"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe sending domain, like example.com.
providerNoYour sending provider, if you know it: adds its selectors and return path to the search.
dkim_selectorsNoYour DKIM selectors (the part before ._domainkey); for Amazon SES, the three Easy DKIM tokens.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.
idempotency_keyNoReuse with the same domain, provider and selectors to retry safely without paying twice; a retry without it is a new purchase.
max_price_centsNoThe most this may cost, in US cents.
inbox_instance_idNoOne of your owner's webhook inboxes: the completion event (domain, score, counts) is written there.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "domain": "example.com",
      +    "idempotency_key": "example-check-1",
      +    "max_price_cents": 100
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Added

TDQS

A4.6/5.0
Behavior4/5

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

Discloses the things annotations cannot: $1 per domain charged from the balance, rate limits (30 checks per owner per 24h, one domain max 5 times per hour), pending_approval for larger orders, and the plain-DNS/no-send scope. It also warns that a full pass does not guarantee inbox delivery, which prevents over-reading of results. The destructiveHint=true annotation is consistent with a paid, balance-spending call, though the description could more explicitly tie the 'destructive' label to the charge.

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?

Front-loads purpose and price, then report contents, then sibling alternatives, then limits and caveats — a sensible order with no filler sentences. It is dense and parenthesis-heavy, which slows parsing slightly, but each clause carries information an agent needs.

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?

Seven parameters, one required, all covered by the schema, and the description still explains cost, limits, approval gating, scope and the shape of the returned report. With no output schema present, the description adequately substitutes by describing score, pass/warn/fail per check and the records to add.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: provider enriches the search with that provider's DKIM selectors and return path, and dkim_selectors should carry the three Easy DKIM tokens for Amazon SES. It also contextualizes cost via $1 per domain, which frames max_price_cents.

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 — checking how the domain the owner sends email from is configured — and enumerates exactly which records are inspected (MX, SPF, DKIM, DMARC, MTA-STS, TLS-RPT, BIMI, rDNS, blocklist). It is immediately distinguishable from get_sender_check and list_sender_checks, which are named as retrieval siblings.

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

Usage Guidelines5/5

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

Explicit routing: re-read results with get_sender_check or list_sender_checks since re-reading is free, only pay for a new check when the setup changed. Also gives conditional guidance for provider and dkim_selectors (including the SES three-token case) and states that bigger orders wait for owner approval.

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.