Skip to main content
Glama

technology_stack

Read-only

Detect a website’s CMS, frameworks and hosting technology for integration planning. 0.005 USDC per request.

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

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http or https URL. Only the host matters for the cache; a path is followed but never probed separately.
renderNoRender the page in a headless browser before matching. Off by default: plain delivery is faster, cheaper on the origin and enough for almost every site. Turn it on for pages that build their markup entirely in JavaScript.
refreshNoBypass the 24 hour cache and fetch the origin again. Same price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive) and the schema explains cache and refresh behavior. The description adds a useful cost figure (0.005 USDC per request), which is real value beyond structured fields, but it says nothing about why idempotentHint is false or how repeated calls may vary.

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 short sentences, purpose first and price second, with no redundant wording. Nothing could be cut without losing information.

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?

For a simple three-parameter, annotation-covered tool this is close to adequate, but with no output schema the description never hints at the shape of the result (e.g., detected CMS/framework/hosting fields) or what happens when nothing is detected. Adding one clause on the return would make it 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 description coverage is 100%, including render and refresh rationale, so the schema already does the heavy lifting. The description adds no parameter-level meaning of its own, so the baseline of 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?

A specific verb-plus-resource statement: detect a website's CMS, frameworks and hosting technology. The scope ('for integration planning') frames the intent well. It does not differentiate itself from the sibling domain_profile, which sounds closely related, so it stops short of 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 only implied via the phrase 'for integration planning'; there is no explicit when-to-use/when-not language and no named alternatives such as domain_profile or ip_reputation. An agent can infer context but must guess at boundaries.

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