Skip to main content
Glama
jrelph

RIPE Atlas MCP Server

by jrelph

RIPE Atlas Traceroute Measurement

atlas_measure_traceroute

Traces the network path from distributed probes to a target using ICMP, UDP, or TCP. Supports customizable hop limits, Paris traceroute, and probe selection by country or ASN.

Instructions

Create a traceroute measurement on the RIPE Atlas network.

Traces the network path from distributed probes to a target, showing each hop.

Args:

  • target (string): Target hostname or IP

  • protocol ('ICMP'|'UDP'|'TCP'): Protocol (default: ICMP)

  • max_hops (1-255): Max TTL (default: 32)

  • paris (0-64): Paris traceroute mode (default: 16, 0=standard)

  • port (1-65535): Destination port (TCP only)

  • 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
targetYesTarget hostname or IP address
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
packetsNoNumber of packets per hop (1-16, default: 3)
sizeNoPacket size in bytes (1-2048, default: 48)
protocolNoProtocol to use: ICMP, UDP, or TCPICMP
timeoutNoTimeout per packet in ms
dont_fragmentNoSet Don't Fragment flag
parisNoParis traceroute variant (0=standard, 1-64=Paris, default: 16)
first_hopNoFirst TTL hop (1-255, default: 1)
max_hopsNoMaximum TTL hops (1-255, default: 32)
portNoDestination port (TCP only)
destination_option_sizeNoIPv6 destination option header size
hop_by_hop_option_sizeNoIPv6 hop-by-hop option header size
Behavior4/5

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

Annotations show readOnlyHint=false, but the description adds context: requires API key with 'create measurement' permission, returns measurement ID(s). It does not mention credit consumption or side effects, but covers key behavioral traits beyond annotations.

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 front-loaded with purpose and has a structured Args section. It includes some explanatory text (e.g., 'Traces the network path...') that is useful but slightly verbose. Overall, it is concise for a complex tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 27 parameters and no output schema, the description covers the creation process and returns measurement ID(s). However, it lacks details on the structure of the returned ID or how to interpret/use it. This leaves completeness gaps for new users.

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?

Input schema has 100% description coverage, so baseline is 3. The description's 'Args' section repeats defaults and descriptions already in the schema, with little added value. Grouping of probe selection parameters is helpful, but overall redundancy keeps score at 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 clearly states 'Create a traceroute measurement on the RIPE Atlas network' and explains it traces the network path. The verb 'Create' and resource 'traceroute measurement' are specific. It distinguishes from sibling tools like atlas_measure_dns by focusing on traceroute.

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?

The description does not provide explicit guidance on when to use this tool versus sibling tools (e.g., atlas_measure_ping). It only implies usage for traceroute, but does not mention alternatives or conditions. Usage is implied but not explicit.

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