Skip to main content
Glama
offsec-mcp

offsec-mcp

by nadirzhon

Analyze Js

analyze_js

Extract secrets, endpoints, and parameters from JavaScript content or a URL to support authorized reconnaissance and security analysis.

Instructions

Extract secrets, endpoints, and parameters from JavaScript (pasted content or a URL).

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": {
      "source": "<source>"
    },
    "name": "analyze_js"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only extraction, but does not disclose whether URL input is fetched over the network, whether JavaScript is executed, whether authentication or rate limits apply, or what safety considerations exist. The output schema covers return values, but key behavioral traits are absent.

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?

The description is a single front-loaded sentence with no wasted words. The purpose and accepted input forms are stated efficiently, and there is no redundant restatement of the tool name.

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?

The tool is simple, has one required parameter, and has an output schema, so the description's coverage of purpose and input forms is enough to attempt a call. However, with no annotations and no schema descriptions for the parameter, missing behavioral context such as network fetching or execution semantics leaves a clear completeness gap.

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 0% for the single 'source' parameter. The description partially compensates by clarifying that source can be pasted JavaScript content or a URL, which is meaningful beyond the bare string schema. It still lacks format details such as URL scheme expectations, size limits, or examples.

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 description states a specific verb, 'Extract,' and names three concrete resource types: secrets, endpoints, and parameters. It also scopes the input to JavaScript, which clearly separates it from the DNS, WHOIS, CVE, HTTP, port-scan, and scope siblings. It does not explicitly name any alternative tool, so sibling differentiation is implicit rather than stated.

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?

The parenthetical 'pasted content or a URL' implies the tool is for JavaScript analysis from either raw input or a fetched script. However, it gives no explicit when-to-use, when-not-to-use, or alternative-tool guidance, leaving the agent to infer usage from the purpose.

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