Skip to main content
Glama

ipinfo

by io.github.pipeworx-io

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYesYour current IP address
orgYesOrganization or ISP name
cityYesCity name associated with your IP address
postalYesPostal code associated with your IP address
regionYesRegion or state associated with your IP address
countryYesCountry code associated with your IP address
latitudeYesLatitude coordinate of your IP geolocation
timezoneYesTimezone associated with your IP address
longitudeYesLongitude coordinate of your IP geolocation

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
  3. First observed

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Several tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer data questions; polymarket_arbitrage, polymarket_edges, and polymarket_edge_tracker all scan prediction markets. Despite long descriptions, an agent could easily select the wrong one, especially the currently identical ask_pipeworx and ask_pipeworx_beta.

Naming Consistency3/5

Mostly snake_case, but with inconsistent patterns: get_my_ip/lookup_ip use verb_noun, entity_profile/recent_changes are noun phrases, remember/recall/forget are bare verbs, and the polymarket_* tools share a brand-prefixed noun style. Readable but not a predictable, uniform convention.

Tool Count2/5

At 33 tools, the server is overloaded, far exceeding the 25-tool threshold for 'too many.' It combines two unrelated identities—the original ipinfo IP lookup and the massive Pipeworx data/research platform—making the toolset heavy and harder for an agent to navigate efficiently.

Completeness4/5

The tool surface provides strong coverage of the data query and research lifecycle: discovery (discover_tools, suggest_questions), entity resolution (resolve_entity), lookup (ask_pipeworx, entity_profile), verification (validate_claim, ask_pipeworx_grounded), and post-processing (search_within, recent_changes). Minor gaps exist—for example, no dedicated 'get SEC filing by accession' tool or single-purpose financials endpoint—but these are workaroundable via the routing tools.

Resources