Skip to main content
Glama
SlanyCukr

Bug Bounty MCP Server

by SlanyCukr

select_tools

Selects optimal security testing tools based on target domain, IP, or URL and scan objectives like comprehensive, fast, stealth, or targeted assessments.

Instructions

AI-powered tool selection based on target profile.

Args: target: Target domain, IP, or URL objective: Scan objective (comprehensive, fast, stealth, targeted)

Returns: Optimized tool selection with recommendations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
objectiveNocomprehensive
targetYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the MCP tool 'select_tools'. It accepts target and objective parameters, logs the action, sends a POST request to the REST API intelligence endpoint for tool selection, and returns the result.
    def select_tools(target: str, objective: str = "comprehensive") -> dict[str, Any]:
        """AI-powered tool selection based on target profile.
    
        Args:
            target: Target domain, IP, or URL
            objective: Scan objective (comprehensive, fast, stealth, targeted)
    
        Returns:
            Optimized tool selection with recommendations
        """
        data = {"target": target, "objective": objective}
    
        logger.info(
            f"🔧 Selecting optimal tools for {target} with {objective} objective"
        )
        result = api_client.safe_post("api/intelligence/select-tools", data)
    
        if result.get("success"):
            logger.info(f"✅ Tool selection completed for {target}")
        else:
            logger.error(f"❌ Tool selection failed for {target}")
    
        return result
  • The @mcp.tool() decorator registers the select_tools function as an MCP tool.
    def select_tools(target: str, objective: str = "comprehensive") -> dict[str, Any]:
  • The docstring defines the input schema (parameters: target (str), objective (str, default='comprehensive')) and output (dict[str, Any]) for the tool.
    Args:
        target: Target domain, IP, or URL
        objective: Scan objective (comprehensive, fast, stealth, targeted)
    
    Returns:
        Optimized tool selection with recommendations
    """
    data = {"target": target, "objective": objective}
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 mentions 'AI-powered' and 'optimized tool selection with recommendations' which gives some behavioral context about what the tool does (makes recommendations rather than executing scans). However, it doesn't disclose important behavioral traits like whether this is a read-only operation, what format the recommendations come in, whether it has rate limits, or what happens with invalid inputs.

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?

The description is appropriately sized with a clear main sentence followed by structured Args and Returns sections. The information is front-loaded with the core purpose stated first. However, the Args/Returns formatting could be more integrated with the natural language description rather than appearing as separate documentation blocks.

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?

Given this is a recommendation/planning tool with 2 parameters and an output schema, the description provides adequate context. It explains what the tool does, what inputs it expects, and what it returns. The output schema existence means the description doesn't need to detail return values. However, for a tool that presumably interacts with many sibling scanning tools, more guidance about how the recommendations relate to those specific tools would be helpful.

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%, so the schema provides no parameter documentation. The description adds some semantic meaning by explaining that 'target' can be a 'domain, IP, or URL' and 'objective' has specific values like 'comprehensive, fast, stealth, targeted'. However, it doesn't fully document both parameters - it doesn't explain what 'target' format is expected or whether all objective values are valid. Baseline would be lower without this partial compensation.

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 clearly states the tool's purpose: 'AI-powered tool selection based on target profile.' It specifies the verb ('select') and resource ('tools'), and distinguishes itself from sibling tools which are all specific scanning/analysis tools rather than a meta-tool for selecting them. However, it doesn't explicitly contrast with all siblings, just implies a different category.

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 when to use this tool (when you need help selecting appropriate scanning tools based on target and objective), but doesn't explicitly state when NOT to use it or name specific alternatives. The context suggests this is a planning/meta tool used before invoking actual scanning tools, but this is only implied rather than explicitly stated.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SlanyCukr/bugbounty-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server