Skip to main content
Glama
SlanyCukr

Bug Bounty MCP Server

by SlanyCukr

optimize_parameters

Generate AI-optimized tool configurations for security testing based on target domain, IP, or URL to enhance bug bounty hunting effectiveness.

Instructions

Optimize tool parameters using AI based on target profile.

Args: target: Target domain, IP, or URL tool: Tool name to optimize parameters for context: Additional context or constraints

Returns: Optimized parameters and configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextNo
targetYes
toolYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'optimize_parameters'. This function registers the tool using @mcp.tool() decorator and implements the logic by proxying the request to the REST API endpoint '/api/intelligence/optimize-parameters' via the BugBountyAPIClient. The function signature defines the input schema: target (str), tool (str), context (str optional).
    def optimize_parameters(
        target: str, tool: str, context: str = ""
    ) -> dict[str, Any]:
        """Optimize tool parameters using AI based on target profile.
    
        Args:
            target: Target domain, IP, or URL
            tool: Tool name to optimize parameters for
            context: Additional context or constraints
    
        Returns:
            Optimized parameters and configuration
        """
        data = {"target": target, "tool": tool, "context": context}
    
        logger.info(f"⚡ Optimizing {tool} parameters for {target}")
        result = api_client.safe_post("api/intelligence/optimize-parameters", data)
    
        if result.get("success"):
            logger.info(f"✅ Parameter optimization completed for {tool}")
        else:
            logger.error(f"❌ Parameter optimization failed for {tool}")
    
        return result
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 burden. It mentions AI-based optimization but doesn't disclose behavioral traits like whether this is a read-only analysis or a configuration change, what permissions or inputs are needed, potential side effects, or performance considerations. The description is too high-level to guide safe or effective use.

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 and front-loaded, with a clear opening sentence followed by structured 'Args' and 'Returns' sections. There's minimal fluff, though the 'Returns' section is redundant given the output schema. Overall, it's efficient but could be more concise by integrating with structured data.

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?

Given 3 parameters with 0% schema coverage and no annotations, the description provides basic parameter semantics and mentions an output, but it's incomplete for an AI-driven optimization tool. It lacks details on how optimization works, error conditions, or integration with sibling tools. The presence of an output schema reduces the need to explain return values, but 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 description coverage is 0%, so the schema provides no parameter details. The description lists parameters in an 'Args' section with brief explanations ('target: Target domain, IP, or URL', etc.), adding some meaning beyond the bare schema. However, it doesn't fully compensate for the coverage gap—e.g., it doesn't specify formats, examples, or constraints for 'tool' or 'context', leaving ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'optimize tool parameters using AI based on target profile,' which provides a general purpose but lacks specificity. It mentions a verb ('optimize') and resource ('tool parameters'), but doesn't clarify what 'optimize' means operationally (e.g., tuning, suggesting, generating) or how it differs from sibling tools like 'select_tools' or parameter-focused tools. The purpose is vague rather than tautological.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, typical scenarios, or exclusions. Given many sibling tools (e.g., 'arjun_parameter_discovery', 'paramspider_mining', 'x8_parameter_discovery'), there's no differentiation, leaving the agent to guess based on the name alone.

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