Ipinfo

Get My Ip

get_my_ip

Read-onlyIdempotent

Get your current IP address with geolocation data. Returns city, region, country, coordinates, org, postal code, timezone.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`ip`	Yes	Your current IP address
`org`	Yes	Organization or ISP name
`city`	Yes	City name associated with your IP address
`postal`	Yes	Postal code associated with your IP address
`region`	Yes	Region or state associated with your IP address
`country`	Yes	Country code associated with your IP address
`latitude`	Yes	Latitude coordinate of your IP geolocation
`timezone`	Yes	Timezone associated with your IP address
`longitude`	Yes	Longitude coordinate of your IP geolocation

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "city": {
+      "description": "City name associated with your IP address",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "country": {
+      "description": "Country code associated with your IP address",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "ip": {
+      "description": "Your current IP address",
+      "type": "string"
+    },
+    "latitude": {
+      "description": "Latitude coordinate of your IP geolocation",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "longitude": {
+      "description": "Longitude coordinate of your IP geolocation",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "org": {
+      "description": "Organization or ISP name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "postal": {
+      "description": "Postal code associated with your IP address",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "region": {
+      "description": "Region or state associated with your IP address",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "timezone": {
+      "description": "Timezone associated with your IP address",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "ip",
+    "city",
+    "region",
+    "country",
+    "latitude",
+    "longitude",
+    "org",
+    "postal",
+    "timezone"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026
- addedInput schema / examples
```
Added value: +[
+  {}
+]
```
First observedApr 14, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds the return field list, which is useful but more about output than behavioral context like side effects or requirements. There is no contradiction with 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?

The description is a single, direct sentence front-loading the purpose and listing key return fields. Every word earns its place with no fluff or redundancy.

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?

This is a simple, zero-parameter tool with comprehensive annotations and an output schema. The description fully captures the tool's purpose and the nature of the returned data, making it complete for effective use.

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?

The tool has zero parameters, so the schema is fully complete and there is no need for parameter explanations. The description appropriately focuses on the return data instead.

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?

The description clearly states the tool retrieves the caller's current IP address with geolocation data. It distinguishes itself from the sibling tool 'lookup_ip' by specifying 'my' (current IP), leaving no ambiguity about its scope.

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

Usage Guidelines3/5

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

The description implies usage for obtaining one's own IP address but does not explicitly state when to use this over alternatives like 'lookup_ip', nor does it mention exclusion criteria. This is a case of implied usage rather than clear guidance.

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

All Ipinfo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.