Skip to main content
Glama
jrelph

RIPE Atlas MCP Server

by jrelph

RIPE Atlas NTP Measurement

atlas_measure_ntp

Create NTP measurements across distributed probes to measure clock offset and delay from any NTP server.

Instructions

Create an NTP measurement on the RIPE Atlas network.

Queries NTP time servers from distributed probes to measure clock offset and delay.

Args:

  • target (string): NTP server hostname or IP

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

  • timeout: Timeout per packet in ms

  • 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 (1-16, default: 3)
timeoutNoTimeout per packet in ms
Behavior4/5

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

Annotations indicate it's a write operation (readOnlyHint=false). The description clarifies the creation nature and adds a requirement for a specific API key permission. No contradictions, but could mention side effects like credit consumption.

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 concise with clear sections for purpose, arguments, returns, and requirements. Every sentence adds value, though it could be slightly more structured.

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?

No output schema is provided; the description states 'Returns: Measurement ID(s)' but does not explain the asynchronous nature or how to retrieve results. Sibling tools for results may infer, but it's not fully self-contained.

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 description coverage is 100%, so the description offers a high-level grouping (e.g., 'Probe selection') but does not add significant new meaning beyond the schema definitions.

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 an NTP measurement' with specific verbs and resource, and the name and title distinguish it from sibling tools like atlas_measure_dns or atlas_measure_ping.

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 mentions the required API key permission but does not explicitly state when to use this tool versus other measurement types or provide any exclusion criteria. Given the many sibling tools, more guidance would help.

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