Skip to main content
Glama

BRAINIAC Web Technology Fingerprinting

Technology stack diff

web-technology_tech-stack-diff
Read-onlyIdempotent

Diff two technology-detect results for added, removed and version-changed technologies. Price $0.02 USDC. POST /api/v1/web-technology/tech-stack-diff. An unpaid call returns the x402 payment terms and does not run.

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-technology_tech-stack-diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoafter, object. Optional.
beforeNobefore, object. Optional.
afterInputNoafterInput, object. Optional.
beforeInputNobeforeInput, object. Optional.

Output Schema

NameRequiredDescriptionDefault
addedNoadded. Array.
removedNoremoved. Array.
sourcesNosources. Array.
unchangedNounchanged. Number.
limitationsNolimitations. Array.
versionChangedNoversionChanged. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world traits, so the bar is lower. The description adds genuinely valuable context beyond them: a $0.02 USDC price, the POST /api/v1/web-technology/tech-stack-diff endpoint, and the fact that an unpaid call returns x402 payment terms instead of executing — critical for an agent to avoid assuming success.

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 sentences with no waste: capability first, then cost, then endpoint, then the payment failure mode. Nothing is repeated and the most decision-relevant facts are front-loaded.

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 tool with a nested schema, four optional top-level parameters and an output schema, the description covers purpose and the payment gate well enough to invoke it. The remaining gap is that it never explains the two mutually exclusive input modes (pre-detected results vs raw URL/HTML input), which an agent would have to reverse-engineer from the schema.

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%, so the baseline applies regardless of what the description says about parameters. The schema labels are boilerplate ('after, object. Optional.'), and the description adds no clarification of the important before/after versus beforeInput/afterInput alternative, which is the main semantic ambiguity in this tool.

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 first sentence gives a specific verb and resource: diff two technology-detect results, returning added, removed and version-changed technologies. It is clearly a downstream operation on the sibling technology-detect tool, though it never names that sibling to route the agent explicitly.

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 by the purpose statement: the agent can infer it should be used once two detect results are available. There is no explicit when-not guidance, no mention of alternatives such as calling technology-detect twice, and no explanation of when to supply pre-computed results versus raw inputs.

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