Crawlora MCP

web_techstack

Read-only

Inspect one public URL and return detected technology records, confidence, version when available, and matching evidence. Use web_scrape for page content or datasets_techstack_search and datasets_techstack_item for stored technology records.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "web_techstack"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No	The absolute http(s) URL to fingerprint.
`render`	No	Fetch strategy used to retrieve the HTML before detection: browser (headless browser that executes JavaScript — the default, so client-injected scripts like analytics, tag managers and pixels are detected), auto (Chrome-impersonated HTTP, escalating to a real browser only when blocked or JS-rendered), or http (HTTP only, no JavaScript — fastest/cheapest, but sees only the server HTML). Defaults to browser.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile and external reach. The description adds which fields come back (confidence, version when available, evidence) but discloses nothing about rate limits, failure behavior on non-public URLs, or analysis latency. With annotations carrying the safety burden and an output schema present, this is adequate but thin.

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 sentences, front-loaded with what the tool does and the outputs, followed by routing to siblings. No filler or repetition.

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 2-parameter read-only tool with an output schema and readOnly/openWorld annotations, the description covers purpose and sibling routing well. It stops short of noting any input constraints (e.g., public-only, single-URL limitation) that would make it fully self-contained.

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 100% – both 'url' and 'render' carry full descriptions in the schema, including the browser/auto/http tradeoffs. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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+resource: 'Inspect one public URL and return detected technology records, confidence, version when available, and matching evidence.' The scope ('one public URL') and the return payload are named, letting an agent distinguish it from web_scrape and the datasets_techstack tools without opening any schema.

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?

Explicitly routes the agent to alternatives: 'Use web_scrape for page content or datasets_techstack_search and datasets_techstack_item for stored technology records.' This clearly demarcates live-URL fingerprinting vs page content vs stored datasets, though it never states an explicit when-not condition for this tool itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?