Skip to main content
Glama

web_tools_tech_detect

[$x402 pago por llamada] Detecta tecnología web (WordPress, Shopify, Next.js, React, Angular, Vue, Astro, Drupal, Joomla, Laravel, Django, etc.) por firmas en headers y HTML.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses two behaviors: it is a paid per-call endpoint (x402) and detection is signature-based on headers and HTML, which implies the page is fetched server-side and JS-only frameworks may not be detected. It does not explain what happens on unreachable/timeout/blocked sites or what the response contains, leaving meaningful gaps for a zero-annotation tool.

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?

One compact sentence plus a bracketed cost tag; the cost signal and the resource are both front-loaded with no filler. Slightly dense (the framework list is long) but every element is informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and no annotations, so the description should say what comes back (detected technologies, versions, confidence, evidence). It covers the input side and the payment model but leaves the return contract and failure modes unspecified — adequate, not complete.

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 50%: x_payment is well documented in the schema (402 fallback behavior), but the required `url` parameter has no description at all. The description's payment tag reinforces the x_payment semantics, yet it adds nothing about the url — e.g., whether a scheme is required or whether redirects are followed.

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 and resource ("Detecta tecnología web") and enumerates the frameworks/CMSs it identifies, plus the detection mechanism ("firmas en headers y HTML"). It is clearly distinct from near-neighbors like net_tools_headers_audit or net_tools_cdn_fingerprint, though it never explicitly contrasts itself with them.

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?

The use case is implied by the name and description (run it against a URL to learn the stack), and the "[$x402 pago por llamada]" prefix warns of cost. However, there is no explicit when-to-use guidance, no mention of net_tools_headers_audit / net_tools_cdn_fingerprint as overlapping alternatives, and no note that the tool requires a reachable public page.

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