Skip to main content
Glama
jrelph

RIPE Atlas MCP Server

by jrelph

RIPE Atlas HTTP Measurement

atlas_measure_http

Create HTTP measurements from distributed probes to a target web server. Configure method, path, port, and probe selection to test web performance and availability.

Instructions

Create an HTTP measurement on the RIPE Atlas network.

Makes HTTP requests from distributed probes to a target web server.

Args:

  • target (string): Target hostname or IP

  • method ('GET'|'HEAD'|'POST'): HTTP method (default: GET)

  • path (string): URL path (default: '/')

  • port (1-65535): Port (default: 80)

  • version (string): HTTP version (default: '1.1')

  • header_bytes: Max header bytes to capture

  • body_bytes: Max body bytes to capture

  • timing_verbosity (0|1|2): Detail level

  • 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
portNoPort number (default: 80)
header_bytesNoMax bytes to retrieve from response header (0=no limit)
versionNoHTTP version (e.g. '1.0', '1.1')1.1
methodNoHTTP methodGET
pathNoURL path (default: '/')/
query_stringNoQuery string to append to path
user_agentNoCustom User-Agent header
body_bytesNoMax bytes to retrieve from response body (0=no limit)
timing_verbosityNoTiming detail: 0=none, 1=basic, 2=per-read
Behavior5/5

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

Annotations indicate non-read-only, non-destructive, non-idempotent, and open-world. The description adds context about requiring an API key with 'create measurement' permission, returning a measurement ID, and making external HTTP requests, which goes beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is fairly long with a bullet list of arguments. It is front-loaded with purpose but repeats some schema information. Could be more concise while maintaining clarity.

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 25 parameters, no output schema, and annotations present, the description covers purpose, return value, permissions, and key parameters. It is complete enough for an agent to understand the tool's functionality and requirements.

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% with descriptions for all 25 parameters. The description adds value by summarizing key parameters (e.g., method, path, port, probe selection) and grouping them, but baseline is 3 due to high coverage; the extra context earns a 4.

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 it creates an HTTP measurement on the RIPE Atlas network, making HTTP requests from distributed probes. This specific verb+resource combination distinguishes it from sibling tools like atlas_measure_ping, atlas_measure_dns, etc.

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 for HTTP measurements but does not explicitly state when to use this tool versus alternatives. Sibling tools exist for other protocols, providing context, but no explicit exclusions or when-not-to-use guidance.

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