Skip to main content
Glama

DomainVet

Detect a website's technology stack

tech_detect
Read-onlyIdempotent

Identify what a site is built with from its HTML and headers: CMS (WordPress, Shopify, Webflow, Ghost...), framework (Next.js, Nuxt, Astro...), CDN/hosting (Cloudflare, Vercel, Netlify...), analytics, payments, support chat and web server. ~50 fingerprints; heuristic.

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_detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesSite URL

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 readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. The description adds genuinely useful calibration beyond that: '~50 fingerprints; heuristic' tells the agent that results are probabilistic and coverage is limited, which should shape how it reports findings. It stops short of describing fetch behavior, timeout, or what happens on non-HTML/JS-rendered pages.

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?

One sentence, front-loaded with the action and evidence source, then a compact enumerated scope and a short accuracy caveat. No redundant restatement of the title or 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, read-only tool with annotations covering safety and no output schema, the description supplies what's needed: what is detected, from what inputs, and how reliable it is. The remaining gap is failure modes — behavior on non-HTML pages or JS-rendered sites — which matters for a heuristic detector.

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?

There is a single parameter with 100% schema coverage ('Site URL'), so the schema does the documentation work and baseline is 3. The description only implies that the URL must be fetchable and that HTML is retrieved; it adds no detail on accepted formats (scheme, subdomains, redirects).

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 (identify) and resource (a site's tech stack) and names the evidence source (HTML and headers). The parenthetical taxonomy (CMS, framework, CDN/hosting, analytics, payments, chat, web server) makes the output scope concrete and clearly separates it from siblings like dns_lookup or security_headers.

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 by 'Identify what a site is built with from its HTML and headers' — the agent can infer this is a page-fetch-based scanning tool rather than a DNS or certificate lookup. However, there is no explicit when-to-use/when-not guidance and no mention of sibling tools to route between, so an agent must infer alternatives from names alone.

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