Skip to main content
Glama

BRAINIAC Web Technology Fingerprinting

Detect web technologies

web-technology_technology-detect
Read-onlyIdempotent

Detect CMS, frameworks, analytics, CDN and widgets from caller-supplied HTML, headers, cookies, scripts and meta with confidence and evidence. Price $0.04 USDC. POST /api/v1/web-technology/technology-detect. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "web-technology_technology-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNourl, string, length 0 to 2000. Optional.
htmlNohtml, string, length 0 to 2097152. Optional.
metaNometa, object. Optional.
cookiesNocookies, array. Optional.
headersNoheaders, object. Optional.
scriptUrlsNoscriptUrls, array. Optional.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
limitationsNolimitations. Array.
technologiesNotechnologies. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the description isn't carrying the safety burden. It goes beyond them with genuinely useful operational facts: results come with confidence and evidence, each call costs $0.04 USDC, the endpoint is POST /api/v1/web-technology/technology-detect, and an unpaid call returns x402 payment terms without executing. That payment/auth gate is exactly the kind of context annotations cannot express.

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 tight sentences: capability first, then cost and endpoint, then the payment-gate caveat. No filler and the most decision-relevant facts are front-loaded. Slightly telegram-style phrasing ('Price $0.04 USDC. POST /api/v1/...') 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?

With an output schema present, the description needn't explain return shapes, and it covers the commercial/auth gate well. The main remaining gap is that all six inputs are optional and the description never says whether at least one (or a specific combination) is required for a meaningful result, which matters for a six-parameter tool.

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 100%, so the schema already documents all six parameters and this scores at the baseline. The description does add a useful hint that detection draws on HTML, headers, cookies, scripts and meta, implicitly explaining why the parameters exist, but adds no format, precedence, or combination rules.

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 (detect) and a specific resource set (CMS, frameworks, analytics, CDN, widgets) plus the input sources it consumes (HTML, headers, cookies, scripts, meta). An agent immediately knows what the tool returns. It stops short of differentiating itself from similar sibling detectors such as ecommerce-platform-detect or payment-provider-detect, which would have earned a 5.

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: 'caller-supplied' inputs signal that the agent must bring its own HTML/headers/cookies rather than the tool fetching a URL server-side. There is no explicit when-to-use rule, no guidance on which of the six optional inputs are needed or sufficient, and no mention of when a sibling detector is the better choice.

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