Skip to main content
Glama
IPGeolocation MCP Server

IPGeolocation MCP Server

Get My IP Address

get_my_ip
Read-only

Retrieve the public IP address of the machine running the MCP server without parameters, API keys, or credits; use it for network identity checks, not geolocation.

Instructions

Returns the public IP address of the machine running this MCP server via GET /v3/getip. Takes no input parameters and requires no API key, account, or credits. Text content contains the IP address; structuredContent contains { ip }. This is not geolocation data. lookup_ip provides location, company, ASN, network, time zone, currency, security and abuse data.

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": "get_my_ip"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
ipNo
pageNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "error": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "assistant_guidance": {
      +          "type": "string"
      +        },
      +        "category": {
      +          "type": "string"
      +        },
      +        "documented_status": {
      +          "type": "boolean"
      +        },
      +        "explanation_hint": {
      +          "type": "string"
      +        },
      +        "guidance": {
      +          "type": "string"
      +        },
      +        "message": {
      +          "type": "string"
      +        },
      +        "retryable": {
      +          "type": "boolean"
      +        },
      +        "source": {
      +          "enum": [
      +            "mcp_server",
      +            "ipgeolocation_api"
      +          ],
      +          "type": "string"
      +        },
      +        "status": {
      +          "maximum": 9007199254740991,
      +          "minimum": -9007199254740991,
      +          "type": "integer"
      +        }
      +      },
      +      "required": [
      +        "source",
      +        "category",
      +        "message",
      +        "retryable",
      +        "guidance",
      +        "assistant_guidance"
      +      ],
      +      "type": "object"
      +    },
      +    "ip": {
      +      "type": "string"
      +    },
      +    "page": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "cursor": {
      +          "description": "Opaque cursor returned in page.cursor or page.next_cursor. Retrieval requires the same server process and API key and does not repeat the original lookup.",
      +          "maxLength": 80,
      +          "pattern": "^[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}:\\d{1,16}$",
      +          "type": "string"
      +        },
      +        "expires_at": {
      +          "description": "ISO timestamp for idle expiry. Successful page reads extend the cache TTL; eviction or process restart can also remove the result.",
      +          "type": "string"
      +        },
      +        "format": {
      +          "const": "structuredContent_json",
      +          "type": "string"
      +        },
      +        "json_fragment": {
      +          "description": "JSON fragment of the original structuredContent. Fragments concatenate in offset order into the complete JSON, including bulk items and errors.",
      +          "type": "string"
      +        },
      +        "next_cursor": {
      +          "description": "Cursor for the next get_cached_result page, absent on the last page. Page reads never call the API or consume credits.",
      +          "maxLength": 80,
      +          "pattern": "^[a-f0-9]{8}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{4}-[a-f0-9]{12}:\\d{1,16}$",
      +          "type": "string"
      +        },
      +        "offset": {
      +          "maximum": 9007199254740991,
      +          "minimum": 0,
      +          "type": "integer"
      +        },
      +        "source_tool": {
      +          "type": "string"
      +        },
      +        "total_chars": {
      +          "maximum": 9007199254740991,
      +          "minimum": 0,
      +          "type": "integer"
      +        }
      +      },
      +      "required": [
      +        "source_tool",
      +        "format",
      +        "json_fragment",
      +        "offset",
      +        "total_chars",
      +        "cursor",
      +        "expires_at"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observedv1.0.10

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (readOnlyHint, openWorldHint), yet the description adds genuinely new behavioral facts: no API key, account, or credits are required, and the address returned is the server host's, not the caller's. It also discloses the response shapes in text and structuredContent, and preempts the most likely misuse by stating it is not geolocation data.

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?

Four short sentences, front-loaded with the core behavior and scoping caveat, with zero filler. The one mildly redundant sentence is the text/structuredContent breakdown, which restates what the existing output schema already declares.

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 zero-parameter, read-only, single-value tool with an output schema and safety annotations already supplied, the description covers everything an agent needs: what it returns, what it costs, what it is not, and which sibling to use otherwise. No meaningful gap remains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters the baseline is 4, and the description reinforces the schema correctly by stating it 'Takes no input parameters' and that additional properties are disallowed. There is no parameter meaning left to add for a parameterless tool.

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 ('Returns the public IP address'), never mind of which machine — explicitly 'the machine running this MCP server' — and names the underlying endpoint GET /v3/getip. It also separates itself from the nearest sibling by declaring 'This is not geolocation data,' so an agent can distinguish it from lookup_ip without opening any schema.

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

Usage Guidelines4/5

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

Provides clear selection context: use this for the bare IP, and 'lookup_ip provides location, company, ASN, network, time zone, currency, security and abuse data' for anything richer, which effectively routes the agent to the right sibling. It stops short of an explicit 'use this when...' clause, so the guidance is strong but implied rather than stated as a rule.

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