Skip to main content
Glama

IP.LS — IP Lookup Service

by ls.ip
OverviewDiscussionsAdmin

Summarize a batch of IPs (country / continent / ASN / network)

ip_summary
Read-onlyIdempotent

Summarize a large batch of IPs into distributions by country, continent, ASN/operator and network prefix, each bucket with a sample of addresses. Use instead of ip_lookup once the input is in the hundreds or thousands — ip_lookup returns every row, which no context window holds. Up to 5000 addresses or 100 hostnames. Counts are per occurrence; nothing is dropped silently (failed → errors, no database record → no_data, unlisted buckets → tail), the same input set always returns the same numbers, and the result is facts only — no datacenter/residential classification, no verdict. DB-IP Lite (CC BY 4.0).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipsYes
topNoBuckets per dimension.
sampleNoSample addresses per bucket.
prefix4NoIPv4 grouping prefix.
prefix6NoIPv6 grouping prefix; /48 = one end-site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / ips / anyOf
      Previous value: -[
-  {
-    "description": "Addresses/hostnames separated by whitespace or commas — the \"paste a column from a log\" form.",
-    "type": "string"
-  },
-  {
-    "description": "e.g. [\"8.8.8.8\",\"1.1.1.1\",\"example.com\"].",
-    "items": {
-      "type": "string"
-    },
-    "maxItems": 5000,
-    "type": "array"
-  }
-]New value: +[
+  {
+    "description": "Whitespace- or comma-separated (paste a log column).",
+    "type": "string"
+  },
+  {
+    "description": "e.g. [\"8.8.8.8\",\"example.com\"].",
+    "items": {
+      "type": "string"
+    },
+    "maxItems": 5000,
+    "type": "array"
+  }
+]
    • removedInput schema / properties / ips / description
      Removed value: -"IPv4/IPv6 addresses and/or hostnames. Each hostname contributes all of its A/AAAA addresses. Items that are invalid or unresolvable are reported in `errors`, they never fail the batch."
    • changedInput schema / properties / prefix6 / description
      Previous value: -"IPv6 grouping prefix. /24 is meaningless for IPv6; /48 is one end-site, /64 one subnet."New value: +"IPv6 grouping prefix; /48 = one end-site."
    • changedInput schema / properties / top / description
      Previous value: -"Buckets listed per dimension, count desc."New value: +"Buckets per dimension."
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations cover safety (readOnly, idempotent, non-destructive), so the bar is lower, yet the description goes well beyond: input caps (5000 addresses / 100 hostnames), per-occurrence counting, explicit non-silent failure routing (errors / no_data / tail), determinism guarantee, and a clear scope disclaimer (facts only, no datacenter/residential verdict), plus data license.

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?

Front-loaded with purpose and dimensions, then routing guidance, then behavioral guarantees. Despite being dense, every clause carries distinct information (limits, counting, error buckets, determinism, scope limits) with no filler or repetition.

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, so the description carries the return-shape burden and does: distributions per dimension, per-bucket sample addresses, and the three catch-all buckets. Combined with the size limits and determinism statement, an agent has everything needed to call and interpret the 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?

Schema coverage is already 80% with per-parameter descriptions for top, sample, prefix4, prefix6, and the ips anyOf. The description adds batch limits and counting semantics but does not explain the meaning or effect of top/sample/prefix parameters beyond what the schema already states, so the baseline of 3 applies.

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 (summarize) plus resource (large batch of IPs) and enumerates the output dimensions: country, continent, ASN/operator, network prefix, with samples per bucket. It also names the sibling it replaces, so an agent can distinguish it from ip_lookup without reading either schema.

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

Usage Guidelines5/5

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

Explicitly says when to switch: 'Use instead of ip_lookup once the input is in the hundreds or thousands,' and gives the reason (ip_lookup returns every row which no context window holds). The when-to-use, the alternative, and the trigger condition are all present.

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

All IP.LS — IP Lookup Service toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources