Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

IP lookup: owner, network range and country (RDAP)

ip_lookup
Read-only

Look up who holds an IP address (v4 or v6) in the regional internet registries' public records (ARIN, RIPE NCC, APNIC, LACNIC, AFRINIC): the holding organisation, network name and range, allocation type, registration country, abuse contact and registry. Use to see which company or ISP an address in a log belongs to. An HTTP call without ip answers for the caller's own address. Registration country, not city location. Example: ip=8.8.8.8. Price $0.002/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": "ip_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipNoPublic IPv4 or IPv6 address (over HTTP, left out: the caller's own address)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, destructiveHint=false and idempotentHint=false, so the safety profile is covered. The description adds genuinely non-structured context: pricing ($0.002/call via x402 USDC or card key, first 25 free, failed calls free) and the consequence that repeats are not free, which corroborates idempotentHint=false.

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, coverage and return fields, then practical constraints and price. It is dense but nearly every clause carries information; the long parenthetical registry list and closing cost sentences are the only mildly heavy parts.

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?

No output schema exists, yet the description names the fields returned (organisation, network name/range, allocation type, country, abuse contact, registry), and it covers auth/payment and the optional-parameter default. Nothing material is missing for a one-parameter read tool.

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?

With 100% schema coverage on a single parameter, the schema already documents that ip is optional and defaults to the caller's address over HTTP. The description restates that behavior and adds an example (ip=8.8.8.8) and the v4/v6 scope, but contributes little meaning the schema does not already carry.

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?

States a specific verb and resource ('look up who holds an IP address (v4 or v6)') and scopes it to named registry records (ARIN, RIPE NCC, APNIC, LACNIC, AFRINIC), then enumerates the returned facts. The line 'Registration country, not city location' sharply separates it from geolocation siblings like ip_geolocate.

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?

Gives an explicit use case ('see which company or ISP an address in a log belongs to') and clarifies the no-argument behavior (caller's own address over HTTP). It implies but never names the alternative tool to use for city-level data, so the routing guidance is clear but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.