Skip to main content
Glama

Tech Detect

tech_detect
Read-onlyIdempotent

What a website is built with, the ecommerce platform, payment processor, CMS, JavaScript framework, analytics, marketing automation, chat widget, ad pixels, CDN, web server and visitor-identification tools it loads. Give a domain or URL ("shopify.com"). Each technology comes back with the evidence that identified it (a response header, a cookie name, a script it loads) so the answer is checkable. Answers "what technology stack does this site use", "does this company use Stripe or Shopify", "what analytics is this site running", "is this site on HubSpot or Marketo".

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "shopify.com"
    },
    "name": "tech_detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesWebsite address, "stripe.com", "www.example.com", or a full https:// URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Website address — \"stripe.com\", \"www.example.com\", or a full https:// URL."New value: +"Website address, \"stripe.com\", \"www.example.com\", or a full https:// URL."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description adds value beyond that by disclosing the return behavior: each detected technology includes the identifying evidence (header, cookie, script), which tells the agent results are verifiable rather than opaque. It omits caveats about detection confidence or site unreachability.

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?

The lead clause front-loads the purpose before the long enumeration, and the example-questions sentence at the end is compact and intent-rich. The technology list is lengthy but each item adds discriminating detail about scope rather than padding. Minor cost: the opening is a noun phrase rather than an action statement, which reads slightly less crisply.

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 no output schema, the description carries the job of explaining returns, and it does so well by specifying that evidence accompanies each detection. Input format, scope, and example intents are all present. The remaining gap is coverage/accuracy behavior for unreachable or unindexed sites, plus any relationship to tech_detect_coverage.

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 required parameter with 100% schema description coverage, and the schema already documents accepted forms ('stripe.com', 'www.example.com', full https URL). The description repeats the same format guidance with an example rather than extending it, so the baseline 3 applies.

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 states a specific verb-and-resource: it identifies the technology stack a website runs, and enumerates the concrete categories returned (CMS, payment processor, JS framework, analytics, CDN, web server). An agent can tell exactly what this tool produces. It does not, however, distinguish itself from the sibling tech_detect_coverage, which a reader would reasonably assume overlaps heavily.

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?

Usage context is clear: it supplies a domain/URL and maps to recognizable intents ('does this company use Stripe or Shopify', 'what analytics is this site running'). That gives an agent solid positive selection signals. It stops short of exclusions or alternatives (e.g., when to prefer tech_detect_coverage or archive-based tools), so it is context without routing guidance.

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.