Skip to main content
Glama

favicon_hash

Fetch a site's favicon, compute its Shodan mmh3 hash (plus MD5/SHA256), and return a ready-to-use http.favicon.hash query to pivot to related hosts.

Instructions

Fetch a site's favicon and compute the Shodan mmh3 hash (plus MD5/SHA256).

Tries the page's , apple-touch-icon, then /favicon.ico. Returns the ready-to-use Shodan query http.favicon.hash:.

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": {
      "url": "<url>"
    },
    "name": "favicon_hash"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does well: it discloses the internal fallback chain (<link rel=icon> → apple-touch-icon → /favicon.ico) and that multiple hash algorithms are returned. It omits error/timeout/redirect behavior and whether fetching requires network egress permissions, which keeps it short of 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?

Three short sentences with zero filler, front-loaded with the action and backend by the concrete return value. Every sentence adds information the agent cannot get from the schema.

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 one-parameter fetch-and-hash tool with no annotations or output schema, the description covers what it does, how it resolves the favicon, and what it returns. Missing only failure-mode behavior, which is minor at this complexity.

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 0% for the single url parameter, so the description must compensate. Saying 'a site's favicon' and describing tag discovery implies url is a page URL rather than a direct image URL, which is genuine added meaning, but no format, scheme, or redirect guidance is given.

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 (fetch a site's favicon, compute hashes) plus the exact output artifact (the Shodan query http.favicon.hash:<hash>). This clearly separates it from a text-hashing sibling like hash_text, which has no network fetch or favicon discovery.

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?

Implies the use case strongly: converting a live site into a Shodan pivoting query. It does not explicitly say when not to use it or name an alternative, but the recon-pivot context is unambiguous from the returned query string.

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