Skip to main content
Glama
IPGeolocation MCP Server

IPGeolocation MCP Server

Network/Routing Info

lookup_network
Read-only

Retrieve route CIDR prefix, connection type, and anycast status for an IPv4 or IPv6 address, or for the server's egress IP when omitted. Use it to inspect network routing details only.

Instructions

Read-only network lookup via GET /v3/ipgeo. Network details require a paid plan. Cost: 1 credit. Returns { network } with route CIDR prefix, connection_type, and is_anycast. If the API omits network data, returns a local error without inventing an HTTP status; credits may already have been used.

ip omitted means the server's public egress IP. force_refresh bypasses cached data, makes a new upstream request, and can consume credits. This response is limited to network data; lookup_ip can return network data together with location, company, ASN, timezone, currency, security, or abuse.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lookup_network"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipNoIPv4 or IPv6 address to look up. Omit to check the server's public egress IP.
force_refreshNoDefault false. When true, bypasses cached network data; a successful refresh makes a new upstream request and can consume credits.

Output Schema

NameRequiredDescriptionDefault
dataNoPresent on success: API result after field selection, redaction, and transport limits.
pageNo
errorNoPresent on failure, with isError: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.3
    • removedOutput schema / properties / data / additionalProperties / anyOf
      Removed value: -[
      -  {
      -    "type": "null"
      -  },
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "array"
      -  },
      -  {
      -    "type": "object"
      -  }
      -]
    • addedOutput schema / properties / data / additionalProperties / type
      Added value: +[
      +  "null",
      +  "boolean",
      +  "number",
      +  "string",
      +  "array",
      +  "object"
      +]
  2. Addedv2.0.1
  3. Removedv2.0.0
  4. Changed1 schema field changedv1.0.15
    • changedInput schema / properties / force_refresh / description
      Previous value: -"Default false. Leave unset unless the user asks to refresh or rerun."New value: +"Default false. Set true only when the user asks to refresh cached network data; a successful refresh makes a new upstream request and can consume credits."
  5. First observedv1.0.10

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond readOnlyHint/openWorldHint by disclosing the paid-plan gate, the 1-credit cost, that force_refresh bypasses cache and burns a credit on refresh, and — importantly — that credits may already have been consumed even when a local error is returned without an invented HTTP status. That billing/failure semantics is exactly the kind of context annotations cannot carry.

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?

Two tight paragraphs with the operation, cost, and return shape front-loaded and parameter behavior in the second. The routing sentence to lookup_ip lands at the very end where it is most easily missed, and the error/credit clause is dense, but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 2-param read tool with annotations and an output schema, this covers everything material: plan requirement, credit cost, cache behavior, error semantics, and sibling differentiation. Return-value documentation is provided even though the output schema already exists, so nothing an agent needs to call it safely is missing.

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 100% and both parameter descriptions already state the omit-means-egress-IP default and the force_refresh caching/credit behavior; the description largely restates the force_refresh semantics in near-identical wording. The one addition is framing force_refresh's cost against the overall 1-credit budget, which is marginal over the schema. Baseline 3 applies.

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 ("Read-only network lookup via GET /v3/ipgeo") and immediately scopes the payload to route CIDR prefix, connection_type, and is_anycast. It also explicitly distinguishes itself from lookup_ip, which returns network data plus location/company/ASN/etc., so an agent can separate the two siblings without reading schemas.

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 the selection rule against the closest alternative: "This response is limited to network data; lookup_ip can return network data together with location, company, ASN...". It also explains the zero-arg default (omit ip to get the server's egress IP) and when force_refresh is warranted, so the agent knows both when to call it and which sibling to prefer.

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