Skip to main content
Glama

tech_fingerprint

Detects servers, CDNs/WAFs, frameworks, CMS, JS libraries and analytics from a URL's headers, cookies and HTML patterns, returning each technology with the evidence that matched.

Instructions

Fingerprint the web stack from headers, cookies and HTML patterns.

Detects servers, CDNs/WAFs, frameworks, CMS, JS libraries and analytics. Returns each technology with the evidence that matched.

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": "tech_fingerprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does usefully disclose the detection inputs and that results pair each technology with its matching evidence, but it is silent on whether the tool performs a live network fetch, how it handles unreachable hosts or redirects, and whether it is read-only in effect.

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?

Three short lines, front-loaded with the core action, with no filler wording. The final sentence about return content could arguably fold into the first line, but nothing is wasted.

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 read tool with no annotations and no output schema, the description covers what the tool does, what data it inspects, and what comes back (technologies plus matched evidence). The main missing piece is operational context: whether it fetches live, and expected failure behavior.

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 description coverage is 0% for the single required 'url' parameter, so the description must compensate. It implies the URL is the target site whose responses are inspected, but gives no format guidance (scheme, hostname-only, path) or constraints such as requiring HTTPS.

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 gives a specific verb and resource ('Fingerprint the web stack') and goes further by naming the signal sources (headers, cookies, HTML patterns) and the technology categories detected. That makes it clearly distinct from siblings like dns_lookup or browser_crawl, though it never names an alternative explicitly.

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 only implied: the agent can infer this is the tool to reach for when it has a URL and wants to know what software backs it. There is no explicit when-to-use versus alternatives (e.g. passive fingerprinting vs. active crawling) and no stated prerequisites such as the host being reachable.

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