Skip to main content
Glama

Urlscan Io Ip

urlscan_io_ip
Read-onlyIdempotent

Search urlscan.io past scan results for a specific IP address (no API key required); returns scan records for pages hosted at or contacting that IP.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
ipYes

Output Schema

NameRequiredDescriptionDefault
tookNoQuery execution time in milliseconds
totalNoTotal number of results for this IP
resultsNoArray of scan results for the IP
has_moreNoWhether more results are available

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds two useful facts beyond that: no API key is needed, and the results cover pages either hosted at or merely contacting the IP, which affects how the agent should interpret hits.

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 front-loaded sentence with the action and scope first and the credential note as a parenthetical. Nothing is redundant, though the parenthetical slightly interrupts the flow of the main clause.

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?

An output schema exists, so return-value detail is unnecessary, and annotations cover the safety profile. For a one-parameter lookup the remaining gaps — result volume, time-range behavior, IP version handling — are minor rather than blocking.

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

Parameters4/5

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

Schema coverage is 0% and the single parameter is a bare unformatted string named 'ip', so the description carries the burden. It specifies the value is a specific IP address (as opposed to a domain or URL), which is the key disambiguation an agent needs; it omits IPv4/IPv6 expectations and formatting.

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 ('Search'), a named resource ('urlscan.io past scan results') and a narrow scope ('a specific IP address'), which is enough to tell it apart from a domain-oriented sibling. It never names urlscan_io_domain or urlscan_io_search, so the differentiation is inferred from the resource rather than stated.

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

Usage Guidelines3/5

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

Includes one genuine usage signal — 'no API key required' — which tells the agent this works without credentials. It gives no explicit when-to-use versus urlscan_io_domain or urlscan_io_search, and no when-not-to-use guidance, leaving routing between the urlscan siblings to inference.

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.