Enumerate hidden directories, files, and virtual hosts by fuzzing URLs in configurable modes. Identifies exposed endpoints for penetration testing through automated brute-force discovery.
Fast web fuzzer for directory/file discovery
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | ||
| mode | No | dirs | |
| consent | No | ||
| dry_run | No | Preview commands/steps without executing the scan | |
| session_id | Yes |
Changes observed during successful MCP inspections.
v3.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must cover behavior. It does not disclose safety concerns (e.g., intrusive nature of fuzzing), rate limits, or authorization needs. The consent parameter implies need for permission but is not explained.
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?
Single sentence, very concise and front-loaded. Could include more critical information without being verbose.
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?
Given 5 parameters, no output schema, and no annotations, the description is incomplete. Missing output format, error handling, and usage contexts.
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?
Schema coverage is only 20% (just dry_run has description). URL, mode, consent, session_id lack explanation. Mode's enum values (dirs, files, vhosts) are not described.
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 clearly states it's a 'fast web fuzzer for directory/file discovery', which defines the tool's purpose. However, it does not mention vhosts or the fuzzing nature explicitly beyond directory and file discovery.
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 on when to use ffuf versus sibling tools like gobuster, wfuzz, or dirb. No prerequisites or context provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.