Skip to main content
Glama
jrelph

RIPE Atlas MCP Server

by jrelph

RIPE Atlas DNS Measurement

atlas_measure_dns

Create DNS measurements on the RIPE Atlas network to query DNS records from distributed probes. Supports custom resolvers, record types, and flags.

Instructions

Create a DNS measurement on the RIPE Atlas network.

Performs DNS lookups from distributed probes. Can query specific DNS servers or use the probe's local resolver.

Args:

  • query_argument (string): DNS name to query (e.g. 'example.com')

  • query_type: Record type (A, AAAA, MX, NS, SOA, TXT, CNAME, DNSKEY, etc.)

  • target (string, optional): DNS server to query. Omit to use probe's resolver.

  • set_rd_bit: Recursion Desired (default: true)

  • set_do_bit: DNSSEC OK flag

  • set_cd_bit: DNSSEC Checking Disabled

  • set_nsid_bit: Request Name Server ID

  • protocol ('UDP'|'TCP'): Transport (default: UDP)

  • probe_count, from_country, etc.: Probe selection

Returns: Measurement ID(s).

Requires: RIPE_ATLAS_API_KEY with 'create measurement' permission.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNoTarget DNS server IP/hostname. If omitted, the probe's resolver is used.
afNoAddress family: 4 for IPv4, 6 for IPv6
descriptionNoHuman-readable description of the measurement
is_oneoffNoIf true (default), run once. If false, run periodically at 'interval'
intervalNoInterval in seconds between measurements (only used when is_oneoff=false)
resolve_on_probeNoResolve DNS names on probe instead of RIPE servers
tagsNoTags to apply to the measurement
response_formatNoOutput format: 'json' for structured data or 'markdown' for human-readablejson
probe_countNoNumber of probes to use (1-1000, default: 5)
from_countryNoTwo-letter ISO country code to select probes from (e.g. 'DE', 'US')
from_asnNoASN number to select probes from
from_prefixNoIP prefix to select probes from (e.g. '193.0.0.0/21')
from_areaNoGeographic area to select probes from
from_probesNoComma-separated list of specific probe IDs to use
include_tagsNoOnly include probes with these tags (e.g. ['system-ipv6-works'])
exclude_tagsNoExclude probes with these tags
query_argumentYesDNS name to query (e.g. 'example.com')
query_typeNoDNS query type (default: A)A
query_classNoDNS query class (default: IN)IN
set_rd_bitNoSet Recursion Desired flag
set_do_bitNoSet DNSSEC OK flag (RFC3225)
set_cd_bitNoSet DNSSEC Checking Disabled flag (RFC4035)
set_nsid_bitNoInclude EDNS Name Server ID request
udp_payload_sizeNoEDNS UDP payload size (512-4096)
protocolNoTransport protocol for DNS queryUDP
retryNoNumber of retries
Behavior4/5

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

The description discloses the creation of a measurement, return of an ID, and API key permission requirement. Annotations indicate readOnlyHint=false and destructiveHint=false. The description adds value beyond annotations by noting the return type and that omitting target uses the probe's resolver.

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 description is well-structured with a lead sentence, purpose paragraph, bulleted arg list, and separate lines for returns and requirements. It is concise but could reduce redundancy (e.g., repeating 'probe_count, from_country, etc.' while schema already covers them).

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?

Given 26 parameters and no output schema, the description covers core functionality, permissions, and probe selection. It mentions 'Returns: Measurement ID(s).' and enumerates key arguments, though it could better explain the response_format parameter or post-creation steps. Overall adequate.

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. The description adds meaning by highlighting key parameters (e.g., query_argument with example 'example.com', query_type list, protocol enum) and summarizing default values, though not all 26 parameters are listed.

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 clearly states the tool creates a DNS measurement on the RIPE Atlas network using distributed probes. It distinguishes from sibling tools (e.g., ping, traceroute) by specifying DNS lookups and enumerating key DNS-specific parameters like query_argument and query_type.

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 description implies usage (perform DNS queries from global probes) and provides context like requiring an API key. However, it lacks explicit when-to-use or when-not-to-use guidance versus alternatives, though the sibling names and tool focus make the purpose clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jrelph/ripe-atlas-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server