Skip to main content
Glama

Internet Quality

internet_quality
Read-onlyIdempotent

Internet Quality Index (IQI) summary, bandwidth, latency, jitter, packet loss, current value + change vs prior period. Optionally filtered to a 2-letter location code.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "location": "US",
      "date_range": "7d"
    },
    "name": "internet_quality"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationNo2-letter location code (e.g., "US", "DE", "JP"). Omit for global.
date_rangeNoLookback window: 1d | 7d | 14d | 28d | 12w | 24w | 52w (default 28d)

Output Schema

NameRequiredDescriptionDefault
latencyYes
locationYesLocation code or GLOBAL
bandwidthYes
range_endYesEnd time of measurement range
date_rangeYesLookback window applied
range_startYesStart time of measurement range
dns_resolutionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "date_range": "7d",
      +    "location": "US"
      +  },
      +  {
      +    "date_range": "28d"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "bandwidth": {
      +      "properties": {
      +        "median": {
      +          "description": "50th percentile (median) value",
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        },
      +        "p25": {
      +          "description": "25th percentile value",
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        },
      +        "p75": {
      +          "description": "75th percentile value",
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        },
      +        "unit": {
      +          "description": "Unit of measurement (e.g., Mbps)",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "date_range": {
      +      "description": "Lookback window applied",
      +      "type": "string"
      +    },
      +    "dns_resolution": {
      +      "properties": {
      +        "median": {
      +          "description": "50th percentile (median) value",
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        },
      +        "p25": {
      +          "description": "25th percentile value",
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        },
      +        "p75": {
      +          "description": "75th percentile value",
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        },
      +        "unit": {
      +          "description": "Unit of measurement",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "latency": {
      +      "properties": {
      +        "median": {
      +          "description": "50th percentile (median) value",
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        },
      +        "p25": {
      +          "description": "25th percentile value",
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        },
      +        "p75": {
      +          "description": "75th percentile value",
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        },
      +        "unit": {
      +          "description": "Unit of measurement (e.g., ms)",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "location": {
      +      "description": "Location code or GLOBAL",
      +      "type": "string"
      +    },
      +    "range_end": {
      +      "description": "End time of measurement range",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "range_start": {
      +      "description": "Start time of measurement range",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "location",
      +    "date_range",
      +    "range_start",
      +    "range_end",
      +    "bandwidth",
      +    "dns_resolution",
      +    "latency"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds useful behavioral context by stating the result includes a current value plus change vs the prior period, telling the agent the payload is comparative rather than a point-in-time snapshot. It does not discuss data freshness, source, or rate limits, so it goes only modestly beyond annotations.

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?

Two sentences, both front-loaded with the metric list first and the optional filter second. Every clause carries information and there is no filler or repetition.

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?

With an output schema present, the description need not explain return values, and rich annotations cover the safety profile, so what remains is a clear metric inventory plus the filter note. It is essentially complete for a two-optional-parameter read tool; only the absence of any usage routing keeps it short of full marks.

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%, and the schema already documents both the 2-letter location code with examples and the full date_range enumeration with a default. The description merely restates the location filter and adds no format, default, or edge-case meaning beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (Internet Quality Index) and enumerates exactly what it returns: bandwidth, latency, jitter, packet loss, current value plus change vs prior period. That is far more concrete than a tautology. It loses a point only because it does not position itself against any alternative tool, though no sibling in the provided list appears to overlap.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The only usage signal is the phrase 'Optionally filtered to a 2-letter location code', which implies the unfiltered call is global but leaves the agent to infer when a location filter is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.