Skip to main content
Glama

ipinfo_lookup

Read-onlyIdempotent

Look up geolocation and ISP details for an IP address, or retrieve them for your own connection when no IP is provided.

Instructions

Get geolocation and ISP info for an IP address (or your own).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ipinfo_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipNoIP address to look up (omit for your own)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered structurally. The description adds only the default-to-caller's-own-IP behavior, which is also in the schema; it says nothing about the data provider, rate limits, or failure modes for invalid IPs.

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?

One sentence, front-loaded with the core capability and the optional-input case noted in parentheses. Efficient with zero waste, though very terse for a tool with several near-duplicate siblings.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only lookup with full param coverage and rich annotations, the essentials are present. However, given the dense cluster of IP-lookup siblings, the description lacks the routing context an agent needs to pick this tool confidently, and there is no output schema to clarify the return shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter's description ('omit for your own') is replicated verbatim in the tool description. Baseline 3 applies since the description adds no format, IPv4/IPv6, or error semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get geolocation and ISP info for an IP address') with the zero-arg convenience case. Clear on its own, but it does not distinguish itself from near-identical siblings such as ip_lookup, ip_address_lookup, or country_by_ip.

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

Usage Guidelines2/5

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

No guidance on when to prefer this over ip_lookup, ip_address_lookup, or country_by_ip, which all appear in the sibling list. The only implied usage is 'call it with an IP'; there are no exclusions or alternative routing.

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