JobsPipe

Detect a company's tech stack

detect_company_tech_stack

Read-only

Detect the technologies a company serves on its domain: frameworks, CDNs, analytics, payments and SaaS widgets, each with a confidence score. Results are cached for 14 days. Costs 1 credit when at least one technology is detected; nothing otherwise. For the technologies a company hires for, from its own job postings, use get_company_tech_stack.

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": {
      "domain": "<domain>"
    },
    "name": "detect_company_tech_stack"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No
`domain`	Yes

Output Schema

Name	Required	Description	Default
`domain`	No
`detected`	No
`scanned_at`	No
`http_status`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026
RemovedSep 23, 2026
AddedSep 22, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and non-destructive, and the description adds material context beyond them: 14-day caching and a conditional cost model (1 credit only when at least one technology is detected). These are billing and staleness facts an agent cannot get from structured fields.

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?

Three tight sentences: capability first, then cost/caching constraints, then the alternative-tool redirect. No filler, and the disambiguation is placed where an agent will read it before invoking.

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?

Return-value explanation is rightly omitted because an output schema exists, and cost/caching are covered. But with an enum parameter at 0% schema coverage, the definition leaves a real decision (which detection mode to pick) undocumented, so it is incomplete for calling the tool correctly.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the parameter burden and it does not: the 'mode' enum (auto/html/render) is never mentioned, nor is the expected domain format (bare hostname vs URL). The only parameter hinted at is 'domain' via the phrase 'on its domain'.

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 and resource ('Detect the technologies a company serves on its domain') and enumerates the categories covered (frameworks, CDNs, analytics, payments, SaaS widgets) with confidence scores. This clearly separates it from data sources like job postings accessed by the sibling tool.

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 get_company_tech_stack when the question is about technologies a company hires for rather than serves on its domain — a genuine routing rule. However, other plausible alternatives such as search_companies_by_technology (reverse lookup) are not addressed, and no other when-not conditions are given.

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

All JobsPipe 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.