Skip to main content
Glama

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

IP address info, classify an IP: tell whether an IP address is public, private, reserved, IPv4 or IPv6

ip_info
Read-only

Classify an IPv4 or IPv6 address without any lookup: version, whether it is private, loopback, link-local, carrier-grade NAT or public, and its integer and reverse-DNS forms (IPv4). Use to triage IPs in logs or allowlists. Example: ip=10.1.2.3. Price $0.01/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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ip": "<ip>"
    },
    "name": "ip_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesThe IP address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond readOnlyHint=true and destructiveHint=false, the description discloses it computes offline with no lookup, that every call is billed ($0.01 via x402 USDC or card key) with 25 free and failed calls free, and that repeats are not free — consistent with idempotentHint=false. This is real added context annotations don't convey.

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-loads purpose and outputs, then usage, then pricing. Dense but each clause (including pricing, which is a genuine cost signal) carries information; slightly packed into one long paragraph.

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

Completeness4/5

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

With no output schema, the description compensates by enumerating the returned classifications and forms. Pricing and auth paths are covered; minor gaps like exact response shape for IPv6 (integer/reverse-DNS noted as IPv4-only) are adequately implied.

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% for the single 'ip' parameter, so the schema does the heavy lifting; baseline 3. The example 'ip=10.1.2.3' adds a small amount of format confirmation but nothing beyond the schema.

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 (classify) and resource (IPv4/IPv6 address) and enumerates exactly what is returned: version, private/loopback/link-local/CGNAT/public, integer and reverse-DNS forms. Phrase 'without any lookup' implicitly separates it from a lookup-based sibling 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 a concrete use case ('triage IPs in logs or allowlists') and notes it works without lookup, steering agents away from geolocation tools. No explicit when-not-to-use clause, but context is clear enough to select correctly.

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.