Skip to main content
Glama

apex-dev

Tech stack detect

tech_stack_detect
Read-onlyIdempotent

Detect the technology stack of any public website (45+ CDNs, hosting, Next.js/React/Vue/Astro frameworks, CMS, analytics, Stripe/payments, auth, security). $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, then call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic website URL or domain to fingerprint (e.g. https://stripe.com).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive, so the description's added value is the x402 payment handshake and the $0.001 per-call cost with specific accepted assets (USDC on Arc/Base/Solana, XNT on X1) — critical behavior an agent cannot infer from annotations. It doesn't describe failure modes (what a call without payment returns, or errors on unpaid retries), leaving some behavioral gaps.

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?

Two dense sentences, front-loaded with capability then the payment protocol, with no filler. Every clause (categories, price, networks, call sequence) carries information the agent needs.

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?

No output schema exists, and the description compensates by enumerating what the fingerprint returns (CDNs, hosting, frameworks, CMS, payments, auth, security) along with cost and payment mechanics. The main remaining gap is the shape of the response (flat labels vs. confidence scores) and error handling, which an agent may want before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema documents both fields and the baseline would be 3. The description adds real meaning beyond the schema by explaining that `payment` is for a second call in a two-step flow and that the first call returns terms — context the schema's "signed x402 payment payload" line does not convey.

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?

Specific verb ("Detect") plus a precisely scoped resource ("technology stack of any public website"), with parenthetical enumeration of detectable categories (CDNs, hosting, frameworks, CMS, analytics, payments, auth, security). This clearly separates it from siblings like security_headers, dns_records, or url_status, which examine single facets rather than the full stack.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit operational sequence: "Call once without `payment` for terms, then call again with `payment`." That is actionable invocation guidance most agents would otherwise get wrong. It stops short of naming an alternative sibling for overlapping questions (e.g., when to use security_headers instead), so not a 5.

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