Skip to main content
Glama

Lookproof DNS, mail and TLS security checks

MX lookup

mx
Read-onlyIdempotent

Use when the user asks which mail servers a domain uses or why it cannot receive mail. Returns MX hosts by preference with addresses, null MX and implicit MX. Provider name: mail_provider; reverse DNS of the servers: domain_health (needs an API key). Ex: 'What are the MX records of example.com?'. Free trial without an API key: a few calls a day.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "mx"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesA public domain name, e.g. example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the description's added value is the return shape (preference-ordered hosts, null MX, implicit MX) and the rate-limit caveat that a free trial works without an API key for a few calls a day. That rate-limit and auth detail is genuinely beyond the annotations. It does not cover error behavior for non-existent or invalid domains, which keeps it short of 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.

Conciseness4/5

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

The usage trigger is front-loaded, followed by return contents, alternatives, an example, and a rate-limit note — a sensible order with little waste. The free-trial sentence is slightly tangential but still actionable for an agent deciding whether the call will succeed.

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 must describe returns, and it does so (preference-ordered MX hosts, addresses, null MX, implicit MX) alongside auth/rate-limit context and sibling routing. It is close to complete for a one-parameter read tool; only failure modes and output granularity (e.g., whether TTLs or raw records are included) are unstated.

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?

There is a single parameter whose schema description coverage is 100% ('A public domain name, e.g. example.com.'), so the schema already carries the semantics. The description only reinforces this indirectly via the example query and adds no constraints or formats beyond the schema, which matches the baseline of 3.

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 states a specific verb and resource ('Returns MX hosts by preference with addresses, null MX and implicit MX') and anchors it to the user questions it answers ('which mail servers a domain uses or why it cannot receive mail'). An agent can distinguish it from siblings like mail_provider or dmarc 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 Guidelines5/5

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

It gives explicit triggering conditions (asking which mail servers a domain uses, diagnosing why mail cannot be received) and names the alternatives with the condition that selects them: mail_provider for provider name, domain_health/API for reverse DNS. Nothing about when to choose this tool is left to inference.

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.