Skip to main content
Glama

BRAINIAC Web Technology Fingerprinting

Favicon MurmurHash3 / SHA-256

web-technology_favicon-hash
Read-onlyIdempotent

Compute Shodan-style MurmurHash3 and SHA-256 of a favicon from raw base64 bytes. Price $0.01 USDC. POST /api/v1/web-technology/favicon-hash. An unpaid call returns the x402 payment terms and does not run.

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": {
      "faviconBase64": "<faviconBase64>"
    },
    "name": "web-technology_favicon-hash"
  }
}

Input Schema

NameRequiredDescriptionDefault
faviconBase64YesfaviconBase64, string, length 1 to 1398202. Required.

Output Schema

NameRequiredDescriptionDefault
mmh3Nommh3. Number.
sha256Nosha256. String.
sourcesNosources. Array.
limitationsNolimitations. Array.
shodanQueryNoshodanQuery. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower. The description adds real context beyond that: the $0.01 USDC price, the concrete endpoint, and crucially that an unpaid call returns x402 payment terms without executing — an agent must know that a 402-style response is not an error.

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?

Four short sentences, front-loaded with the action, then price, endpoint, and payment fallback. Minimal waste; the endpoint path is arguably noise for an MCP caller but is justifiable for a metered HTTP-backed tool.

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?

The tool has an output schema, so return values need no explanation, and there is only one fully documented parameter. The two things an agent could not otherwise know — the cost and the unpaid-call behavior — are both covered, making the definition complete for this complexity level.

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 parameter, so the schema already documents the field and its size bounds. The phrase 'raw base64 bytes' adds a hint about input encoding but is ambiguous — it does not clarify whether a data: URI prefix is accepted or stripped, so semantic value beyond the schema is marginal.

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?

The description names a specific verb and resource: compute Shodan-style MurmurHash3 and SHA-256 hashes of a favicon. It also pins the input form ('raw base64 bytes'), so an agent knows exactly what this does and that no sibling tool (tech-detect, manifest-audit, etc.) performs this hashing function.

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?

Usage is implied rather than stated: an agent infers it should call this when it needs favicon hashes for Shodan-style lookups. There is no explicit when-to-use/when-not guidance or reference to alternatives, though the payment precondition partially serves as a 'call this only if you can pay' signal.

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.

Resources