Skip to main content
Glama

Result

result
Read-onlyIdempotent

Full result by scan uuid. urlscan.io now requires a (free) account API key to fetch full scan results: pass it as _apiKey. Scan summaries are still available keyless through urlscan_io_search.

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": {
      "uuid": "12345678-1234-1234-1234-123456789012"
    },
    "name": "result"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYes
_apiKeyNoYour urlscan.io API key (required by urlscan.io for full results)

Output Schema

NameRequiredDescriptionDefault
dataNoDetailed scan data including requests and resources
metaNoAdditional metadata
pageNoPage information including title, domain, IP
taskNoTask metadata and configuration
statsNoScan statistics

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / _apiKey
      Added value: +{
      +  "description": "Your urlscan.io API key (required by urlscan.io for full results)",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "uuid": "12345678-1234-1234-1234-123456789012"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "description": "Full scan result details",
      +  "properties": {
      +    "data": {
      +      "description": "Detailed scan data including requests and resources",
      +      "type": "object"
      +    },
      +    "meta": {
      +      "description": "Additional metadata",
      +      "type": "object"
      +    },
      +    "page": {
      +      "description": "Page information including title, domain, IP",
      +      "type": "object"
      +    },
      +    "stats": {
      +      "description": "Scan statistics",
      +      "type": "object"
      +    },
      +    "task": {
      +      "description": "Task metadata and configuration",
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: urlscan.io now requires a free account API key for full results and the key is passed as _apiKey, which the agent would not otherwise know. It does not mention rate limits or quota behavior, keeping it below a 5.

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?

Two sentences, zero waste, with the core operation front-loaded and the auth constraint immediately after it. Nothing is repeated from the schema or annotations unnecessarily.

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?

For a two-parameter read tool with full annotations and an output schema, the description covers the operation, identifier, auth requirement, and fallback sibling. The only minor gap is any hint about response size or pagination for full results, which is a small omission.

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 only 50%, and the uuid property has no description in the schema, so the description's clarification that the argument is a scan uuid adds real meaning. It also explains the purpose and requirement of the otherwise opaque _apiKey parameter, compensating for the thin 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?

The description states a specific verb and resource ('Full result by scan uuid') plus the required identifier, which is enough to distinguish it from the summary-oriented sibling. It stops short of a crisp one-line definition, but an agent can tell what it fetches.

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?

It names the alternative explicitly: use urlscan_io_search for keyless scan summaries, and only use this tool when you have an API key for full results. That is a clear routing condition, though it does not spell out exclusions such as when a summary is sufficient versus when full results are necessary.

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.