Skip to main content
Glama

Prefix Overview

prefix_overview
Read-onlyIdempotent

"Prefix overview for [CIDR]" / "info on IP block [X/Y]", comprehensive summary for an IP prefix: BGP announcements, origin ASes, allocation history. Use to understand a whole IP block at once instead of chaining bgp_state + whois.

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": {
      "resource": "8.8.8.0/24"
    },
    "name": "prefix_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourceYesPrefix (e.g. "8.8.8.0/24")

Output Schema

NameRequiredDescriptionDefault
dataNoComprehensive prefix overview with announcements, origins, allocation
statusNoAPI response status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "resource": "8.8.8.0/24"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "data": {
      +      "description": "Comprehensive prefix overview with announcements, origins, allocation",
      +      "type": "object"
      +    },
      +    "status": {
      +      "description": "API response status",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so safety is covered. The description still adds value by disclosing what the aggregate actually contains (announcements, origin ASes, allocation history), telling the agent it is a composite query rather than a single source lookup. It stops short of noting freshness or coverage limits of the allocation history.

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

Conciseness4/5

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

Front-loaded with the action and payload in the first clause, and the last sentence earns its place by routing to alternatives. The two quoted user-phrase aliases are slightly redundant with the surrounding sentence but plausibly aid query matching.

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 and full parameter documentation, the description only needs to convey scope and composition, which it does. Minor gap: no statement about data sources, freshness, or behavior on prefixes with no announcements.

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?

One parameter at 100% schema coverage with a worked example, so the schema carries the burden. The description only echoes the format via '[CIDR]' and '[X/Y]' notation, adding no constraints such as whether host bits are normalized or whether v6 prefixes are accepted.

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?

States a specific verb and resource: a 'comprehensive summary for an IP prefix' covering BGP announcements, origin ASes, and allocation history. The quoted alias phrasings ('Prefix overview for [CIDR]', 'info on IP block [X/Y]') make the match surface explicit, and it names the sibling it replaces.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use ('understand a whole IP block at once') and an explicit alternative ('instead of chaining bgp_state + whois'). An agent can decide between this and the point-query tools without further reading.

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.