Skip to main content
Glama

Ipify

by io.github.pipeworx-io

Ipv4

ipv4
Read-onlyIdempotent

Caller's IPv4 (gateway egress IP).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYesIPv4 address of the caller

Schema Changelog

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

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "ip": {
+      "description": "IPv4 address of the caller",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ip"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint as true and destructiveHint as false. The description adds no behavioral details beyond the return value, which is acceptable given annotation coverage.

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 extremely concise (5 words), front-loaded with the key information, and every word is necessary.

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?

Given no parameters and rich annotations, the description fully informs the agent about the tool's output. The presence of an output schema further reduces the need for detail.

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?

No parameters exist, and schema description coverage is 100%. The description does not need to add parameter info, aligning with the baseline score of 4 for zero-parameter tools.

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 explicitly states the tool returns the caller's IPv4 (gateway egress IP), clearly distinguishing it from sibling tool 'ipv6'.

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?

The description implies usage when the agent needs the caller's public IPv4 address. It does not explicitly state when to use versus alternatives, but the sibling 'ipv6' provides a clear contrast.

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

All Ipify 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

Multiple tools overlap conceptually, e.g., ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research all perform data retrieval, and bet_research / polymarket_edges / polymarket_arbitrage cover prediction markets with unclear boundaries. This overlap forces agents to carefully read descriptions to pick the right tool.

Naming Consistency3/5

Naming is mostly snake_case but inconsistent in pattern: some are verb_noun (compare_entities), some are noun_verb (ai_visibility_check), and some are bare nouns (ipv4) or bare verbs (forget). While readable, the lack of a uniform pattern reduces predictability.

Tool Count2/5

33 tools is high for a single server, especially given the server name 'Ipify' which implies a simple IP lookup service. The broad range (from memory ops to prediction market analysis) suggests the tool set is a collection of utilities rather than a coherent, scoped API.

Completeness2/5

The tool set lacks focus: for a server named 'Ipify', basic IP geolocation or ASN lookup is missing. As a general toolkit, it covers many areas superficially but has significant gaps (e.g., no tools for updating or deleting data, no domain-specific lifecycle).

Resources