Identifies the technology stack of web applications by analyzing a target URL, enabling reconnaissance for bug bounty security assessments.
Web 指纹识别（纯 Node.js 实现）
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | 目标 URL |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations are absent, so the description bears full responsibility for behavioral disclosure. It only says it performs fingerprint identification and is implemented in pure Node.js; it does not mention whether it sends network requests, is read-only, has rate limits, or what side effects it may have on the target.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single compact phrase, front-loaded with the main purpose ('web fingerprint identification') followed by the implementation detail. There is no filler or redundancy, though it is barely a sentence.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and very little information, the agent is left uncertain about what the tool returns, how to interpret results, and why to choose this over the sibling 'web-fingerprint'. The description is too thin for a security-scanning tool that may have operational implications.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema covers 100% of parameters and describes 'url' as '目标 URL' (target URL), which is straightforward. The description adds no additional meaning about format, required scheme, or edge cases, so it meets the baseline but provides no extra value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb+resource: 'Web 指纹识别' (web fingerprint identification), which identifies web technologies/applications. It adds the implementation detail 'pure Node.js implementation', but it does not clarify what exactly is fingerprinted or how the 'lite' variant differs from the sibling 'web-fingerprint'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus 'web-fingerprint' or other lite tools. The only contextual hint is the 'pure Node.js' implementation, which implicitly suggests a standalone lightweight version, but no explicit conditions, alternatives, or exclusions are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.