Skip to main content
Glama

peeringdb_network

Look up a network’s PeeringDB profile by ASN or name to review peering policy, internet exchange, and facility presence.

Instructions

PeeringDB network profile by ASN (AS15169) or name: policy, IX and facility presence.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "peeringdb_network"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a read-only profile lookup and discloses what kind of data comes back (policy, IX and facility presence), but says nothing about authentication, rate limits, whether a name can match multiple networks, or what happens on a miss.

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?

One sentence, front-loaded with the resource, then the accepted input forms, then the returned content. Nothing is redundant or padded.

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?

For a one-parameter read tool with no output schema and no annotations, the description covers the resource, the input forms, and the data categories returned, which is close to sufficient. Only the absence of any auth or error/ambiguity behavior keeps it short of full completeness.

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 coverage is 0% and the single "query" property is described only as a string, so the description must compensate. It does add real meaning by naming the two accepted input forms and giving a concrete ASN example ("AS15169"), but it omits casing, AS-prefix, and partial-name matching rules.

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?

States a specific verb+resource: a PeeringDB network profile, and names the two accepted identifiers ("ASN (AS15169) or name") plus the content returned ("policy, IX and facility presence"). It does not explicitly distinguish itself from the sibling asn_lookup, which likely also accepts an ASN, so an agent could hesitate between them.

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?

The description gives no when-to-use, when-not, or alternative-tool guidance. It never says to prefer asn_lookup for raw ASN data or whether a name lookup is a fallback; the agent must infer the use case entirely from the resource name.

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