Loading ToolBench
MCP server providing access to Globalping, a global network measurement platform for running ping, traceroute, DNS, MTR, and HTTP tests from thousands of locations worldwide
Strong overall definition quality with excellent tool compositions, well-structured schemas, and comprehensive descriptions. All 10 tools have clear descriptions (avg 156 chars, within baseline 194). All tools use proper Zod schema definitions with typed parameters. Tool naming follows verb_noun conventions (ping, traceroute, dns, mtr, http, locations, limits, getMeasurement, compareLocations, help). Annotations present on all measurement tools. Key strengths: input validation (public IP checks), structured output schemas, sensible defaults (limit=3, packets=3). Weak point: output schemas use z.any() for results arrays, losing type specificity. Error handling is present but could be more granular (current approach wraps all errors generically). Per-tool variance ranges from 75-82, indicating consistent quality.
Get a guide on how to run comparison tests using the exact same probes as a previous measurement. Use this tool when you need to benchmark different targets from the same vantage points.
Resolve DNS records (A, AAAA, MX, etc.) for a domain from global locations. Use this tool to verify DNS propagation, troubleshoot resolution failures, or check if users in different regions are seeing the correct records. Note: Only public endpoints are supported. Private networks cannot be tested.
Retrieve the full details of a past measurement using its ID. Use this tool to access raw JSON data, individual probe results, or cached measurements when the initial summary is insufficient.
Get a comprehensive guide to the Globalping MCP server. Use this tool to learn about available tools, understand location formatting (magic fields), or see example usage patterns.
Perform HTTP requests to a URL from global locations. Use this tool to check website availability, measure response times, verify content from different regions, or test API endpoints.
Output schema uses z.any() for results arrays, losing type specificity and making downstream tool integration harder for LLMs to reason about result structure
Tool naming uses camelCase (getMeasurement, compareLocations) instead of snake_case (get_measurement, compare_locations), inconsistent with verb_noun baseline convention used by 90% of A+ tools
Error handling wraps all tool failures with handleToolExecution(), which returns generic error text without categorizing errors as retryable, user-fixable, or fatal. LLMs cannot determine appropriate recovery strategy
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-21 | B | 72 | 2025-06-18+ | v2 |
| 2026-03-09 | D | 50 | - | v1 |
Show your current free test allowance and credits for the Globalping API. The rate limit is the free hourly allowance, not a hard cap: authenticated users with credits can run additional tests beyond the free limits.
List all available Globalping probe locations and how to use them in your tests. Use this tool to discover what locations are available for measurements and understand the Globalping magic field syntax.
Perform an MTR (My Traceroute) test combining the functionality of ping and traceroute from global locations. Use this tool to perform continuous latency and loss measurements to understand network performance and routing behavior over time.
Measure network latency, packet loss, and reachability to a target (domain or IP) from globally distributed probes. Use this tool to check if a server is online, debug connection issues, or assess global performance. Note: Only public endpoints are supported. Private networks cannot be tested.
Trace the network path to a target (domain or IP) from global locations. Use this tool to identify where packets are being dropped, analyze routing paths, or pinpoint latency sources in the network. Note: Only public endpoints are supported. Private networks cannot be tested.
Parameter descriptions in http tool lack expected format guidance, 'target' accepts domain or IP but no regex/format constraint documented; 'path' and 'query' could benefit from example patterns to guide LLM input
getMeasurement and compareLocations tools have minimal input/output documentation, compareLocations takes no input but returns unspecified output, making it unclear what the agent should expect