feroxbuster-mcp

feroxbuster_status

Retrieve the status of a feroxbuster scan, with an option to show a specific number of tail lines from the output.

Instructions

Check the status of a running or completed feroxbuster scan

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": "feroxbuster_status"
  }
}

Input Schema

Name	Required	Description	Default
`tail_lines`	No	Number of lines to show from output (default: 50)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 19, 2026

TDQS

B3.4/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 full burden. It states 'Check the status' but does not disclose whether it reads state, requires a running scan, or returns any specific output format. Missing key behavioral details.

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 sentence of 8 words, with zero waste. It is front-loaded and efficient for the purpose stated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool (one optional parameter, no output schema), the description is too minimal. It does not explain what status information is returned, how to interpret it, or any prerequisites like an active scan. More context is needed for effective use.

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 coverage is 100% for the single parameter, which already includes a description. The tool description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 clearly states the tool checks status of a feroxbuster scan, with specific verb and resource. It distinguishes from sibling tools like feroxbuster_results (for results) and feroxbuster_stop (for stopping).

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 description implies usage for checking progress but does not explicitly state when to use versus alternatives like feroxbuster_results or feroxbuster_config. No when-not or context guidance is provided.

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

Deploy Server