Skip to main content
Glama
Sign In
mx-route-mcp

mx-route-mcp

by MauiGrowth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get DNS records for a domain

get_dns_records
Read-onlyIdempotent

Retrieve the DNS records needed at your registrar for a domain, including MX, SPF, DKIM, and verification entries. Read-only; it does not change DNS settings.

Instructions

Returns the DNS records to configure at the registrar for a domain: MX records, SPF, DKIM (when available) and the verification record. Read-only; it does not change DNS.

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name on the MXroute account, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), and the description reinforces it with 'it does not change DNS.' It adds real behavioral value beyond the annotations with 'DKIM (when available)', warning that the result set can be partial and the agent should not assume a DKIM record is returned.

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?

Two tight sentences: the first front-loads what is returned, the second disambiguates the mutation risk. No filler and nothing redundant with the title.

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 correctly carries the burden of describing return contents and flags conditional DKIM availability. It leaves minor gaps — output format and whether records include priority/TTL values — but is otherwise sufficient for a single-parameter read tool.

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 required parameter and schema description coverage is 100%, so the schema already documents the domain argument with an example. The description adds nothing about the domain parameter (e.g. whether it must be an existing account domain), so baseline 3 applies.

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 (returns DNS records for a domain) and enumerates the exact record types returned: MX, SPF, DKIM and the verification record. This clearly separates it from adjacent siblings such as get_domain_verification_key and get_domain.

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?

The phrase 'to configure at the registrar' makes the intended scenario explicit — this is the tool for domain DNS setup. It stops short of naming alternatives or exclusions (e.g. when to prefer get_domain_verification_key alone), which keeps it below a 5.

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

Deploy Server

Other Tools