Skip to main content
Glama

BRAINIAC Web Technology Fingerprinting

JS library vulnerability detect

web-technology_js-library-vuln-detect
Read-onlyIdempotent

Identify front-end JS libraries from script URLs or contents via Retire.js extractors and list known vulnerabilities. Price $0.04 USDC. POST /api/v1/web-technology/js-library-vuln-detect. An unpaid call returns the x402 payment terms and does not run.

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": {
      "scripts": "<scripts>"
    },
    "name": "web-technology_js-library-vuln-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
scriptsYesscripts, array. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
findingsNofindings. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: it costs $0.04 USDC and an unpaid call returns x402 payment terms without executing the scan — critical operational context 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with purpose and followed by pricing and endpoint facts. Every sentence carries operational value; the raw 'POST /api/v1/...' path is mildly redundant but harmless.

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 an output schema handling return values, full param coverage, and rich annotations, the description only needed to add the payment-gating behavior — which it does. It could be slightly stronger with a note on expected scan latency or size limits on the scripts array, but nothing essential is missing.

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 url and content are already documented with types and length limits. The description only restates the url-or-content duality and does not add per-item guidance (e.g., which field takes precedence or whether one item can supply both), 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?

The description names a specific verb ('Identify'), a specific resource ('front-end JS libraries'), the mechanism ('Retire.js extractors'), and the outcome ('list known vulnerabilities'). This clearly separates it from generic siblings such as web-technology_technology-detect without needing to name them.

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: the phrase 'from script URLs or contents' hints at the two input modes but there is no statement of when to pick this tool over technology-detect or tech-stack-diff, and no exclusions or prerequisites. An agent must infer the scenario.

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