ipv6Caller's IPv6 (gateway egress IP, IPv4 fallback).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| ip | Yes | IPv6 address of the caller (IPv4 fallback) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {}
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "ip": {
+ "description": "IPv6 address of the caller (IPv4 fallback)",
+ "type": "string"
+ }
+ },
+ "required": [
+ "ip"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description adds behavioral context beyond annotations: it returns the caller's egress IP with IPv6 primary and IPv4 fallback. Annotations already indicate read-only, idempotent, open-world behavior, and description aligns without contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence of 6 words with no redundancy. Front-loaded and efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless tool with an output schema, the description is sufficient. No additional context needed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist, so schema coverage is 100%. The description does not need to add parameter information. Baseline for zero parameters is 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it returns the caller's IPv6 address with IPv4 fallback. It implicitly distinguishes from the sibling 'ipv4' tool by mentioning fallback, but lacks explicit differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like 'ipv4'. The context hints at purpose but does not explicitly state when to prefer one over the other.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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 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.
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.
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).