Skip to main content
Glama
jrelph

RIPE Atlas MCP Server

by jrelph

RIPE Atlas Ping Measurement

atlas_measure_ping

Send ICMP echo requests from distributed RIPE Atlas probes to a target host to measure network reachability and latency. Customize probe selection, packet parameters, and address family.

Instructions

Create a ping measurement on the RIPE Atlas network.

Sends ICMP echo requests from distributed probes worldwide to a target host.

Args:

  • target (string): Target hostname or IP address

  • af (4|6): Address family (default: 4)

  • packets (1-16): Number of packets (default: 3)

  • size (1-2048): Packet size in bytes (default: 48)

  • probe_count (1-1000): Number of probes (default: 5)

  • from_country/from_asn/from_prefix/from_area/from_probes: Probe selection

  • is_oneoff (bool): One-shot measurement (default: true)

  • response_format ('json'|'markdown'): Output format

Returns: Measurement ID(s) and link to results.

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 to send (1-16, default: 3)
sizeNoPacket size in bytes excluding headers (1-2048, default: 48)
packet_intervalNoTime between packets in ms (2-30000, default: 1000)
Behavior4/5

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

Annotations already show destructiveHint=false and readOnlyHint=false, but the description adds important context: it requires an API key with 'create measurement' permission, and explains it creates a measurement and returns IDs plus a results link. It does not disclose cost implications or asynchronicity, which would improve transparency.

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?

The description is concise (≈150 words), front-loaded with the main purpose, followed by a compact param summary and essential notes on returns and permissions. Every sentence contributes meaningfully.

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 19 parameters, one required, and no output schema, the description provides a reasonable overview. It covers the primary action, key parameters, return format, and auth requirement. However, it omits that measurements are asynchronous and that results are fetched later via atlas_get_results.

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?

Schema coverage is 100%, so the description's brief param list adds no new information beyond defaults and ranges already in the schema. The description does not clarify relationships between parameters (e.g., from_country vs from_probes) or provide examples, so it only meets the baseline.

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 ping measurement' and specifies it sends ICMP echo requests. It distinguishes from sibling tools like atlas_measure_dns or atlas_measure_http by explicitly naming 'ping' and 'ICMP'.

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?

No explicit when-to-use or when-not-to-use guidance is provided. While the description implies usage for ping/ICMP measurements, it does not compare with siblings or note prerequisites (e.g., 'Use for latency checks; not for DNS resolution'). The lack of explicit alternatives lowers the score.

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