Skip to main content
Glama
IPGeolocation

IPGeolocation MCP Server

by IPGeolocation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Currency and Country Metadata

lookup_currency
Read-only

Read-only currency and country metadata lookup via GET /v3/ipgeo. Works on free and paid plans. Cost: 1 credit per successful lookup.

Instructions

Read-only currency and country metadata lookup via GET /v3/ipgeo. Works on free and paid plans. Cost: 1 credit per successful lookup.

Returns { currency, country_metadata }: currency code/name/symbol plus country calling_code, tld, and languages. ip selects the IP used to derive country and currency; omit it for the server machine's public egress IP. force_refresh bypasses cached data, makes a new upstream request, and can consume credits.

This response is limited to currency and country metadata. lookup_ip can return these fields together with other IP data.

Input Schema

NameRequiredDescriptionDefault
ipNoIPv4 or IPv6 address whose country determines the returned currency and country metadata. Omit to use the server's public egress IP.
force_refreshNoDefault false. When true, bypasses cached currency/country 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. Changed3 schema fields changedv2.0.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / ip / description
      Previous value: -"IPv4 or IPv6 address whose country determines the returned currency and country metadata. Omit to use the caller's IP."New value: +"IPv4 or IPv6 address whose country determines the returned currency and country metadata. Omit to use the server's public egress IP."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": {
+        "anyOf": [
+          {
+            "type": "null"
+          },
+          {
+            "type": "boolean"
+          },
+          {
+            "type": "number"
+          },
+          {
+            "type": "string"
+          },
+          {
+            "type": "array"
+          },
+          {
+            "type": "object"
+          }
+        ]
+      },
+      "description": "Present on success: API result after field selection, redaction, and transport limits.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "error": {
+      "additionalProperties": false,
+      "description": "Present on failure, with isError: true.",
+      "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"
+    },
+    "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"
+}
  3. Changed2 schema fields changedv2.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / force_refresh / description
      Previous value: -"Default false. Set true only when the user asks to refresh cached currency/country data; a successful refresh makes a new upstream request and can consume credits."New value: +"Default false. When true, bypasses cached currency/country data; a successful refresh makes a new upstream request and can consume credits."
  4. Changed2 schema fields 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 currency/country data; a successful refresh makes a new upstream request and can consume credits."
    • changedInput schema / properties / ip / description
      Previous value: -"IPv4 or IPv6 address to look up. Omit to check the caller's IP."New value: +"IPv4 or IPv6 address whose country determines the returned currency and country metadata. Omit to use the caller's IP."
  5. First observedv1.0.10

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark this read-only and open-world, and the description goes well beyond them: 1 credit per successful lookup, cache behavior, that force_refresh triggers a new upstream request and can consume credits, and the default egress-IP behavior when ip is omitted. These are exactly the cost and side-effect facts an agent cannot get from structured fields.

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 purpose, cost, and return shape, then the scoping note against lookup_ip — a sensible order. The return-value sentence duplicates what the output schema already provides, which is the one piece that doesn't fully earn its place.

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, zero-required, read-only lookup with a full output schema and 100% schema coverage, the description covers cost, caching, default behavior, and sibling routing. Nothing an agent needs to invoke it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, and the description adds real meaning by framing ip as the selector of which country/currency is derived and by spelling out the credit implication of force_refresh. It largely restates the schema's own parameter text, so it adds value but not much new syntax or edge-case guidance.

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 states a specific verb and resource ("read-only currency and country metadata lookup") plus the underlying endpoint, and explicitly differentiates from the sibling lookup_ip. An agent can distinguish this from lookup_ip, lookup_network, and lookup_company without opening a schema.

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?

It names the alternative (lookup_ip) and the exact condition that selects it — when you want these fields alongside other IP data. It also states plan availability, credit cost per lookup, and the credit consequence of force_refresh, so the agent can reason about when to call this versus alternatives and when to avoid the refresh flag.

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

Deploy Server

Other Tools