Loading ToolBench
MCP server providing access to Globalping, a global network measurement platform. Enables ping, traceroute, DNS, MTR, and HTTP tests from thousands of locations worldwide.
Strong tool definitions with comprehensive descriptions (avg 180+ chars) and well-structured Zod schemas. All 10 tools have clear, actionable descriptions explaining WHAT, WHEN, and WHY. Input schemas are properly typed with enums, ranges, and constraints. Output schemas documented via Zod. Error handling includes validation (isPublicTarget) and recovery guidance. Main gaps: tools 8-10 lack visible input schema definitions in source; some parameter descriptions could be more concise; no explicit per-tool permission declarations or audit logging patterns.
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 an HTTP request to a URL from global locations. Use this tool to check website availability, measure response times, or verify HTTP status codes from different regions.
Tools 8-10 (getMeasurement, compareLocations, help) lack visible input schema definitions in source code. Only tool names and descriptions are shown; Zod schemas not found in provided src/index.ts excerpt.
No explicit permission declarations (e.g., 'read:network', 'write:none') on any tool. Agents cannot determine least-privilege scope or audit what permissions each tool requires.
No audit logging or request tracing visible. Agent calls (who, what, when, parameters) are not logged for compliance or incident response.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 63 | 2025-06-18+ | v2 |
Show your current rate limits for the Globalping API. Returns rate limit information including requests remaining and reset time.
List all available Globalping probe locations. Returns a list of probe locations grouped by continent and country, including magic field syntax for location selection.
Perform an MTR (My Traceroute) test to a target, combining ping and traceroute functionality. Use this tool to get detailed hop-by-hop statistics including latency and packet loss at each hop.
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 for 'locations' are verbose (200+ chars) and include example values ('US', 'Europe', 'London+UK'). LLMs may reuse examples literally instead of adapting to context.
Tools 'locations' and 'limits' have empty input schemas ({}), making them discovery-only. No parameters to constrain or filter results; agents cannot request specific subsets.