Skip to main content
Glama
stanfrbd

Cyberbro MCP Server

by stanfrbd
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_web_url

Retrieve the web GUI URL for a given analysis ID to view results directly in the browser.

Instructions

Get the web GUI URL for a given analysis ID. Args: analysis_id: Analysis ID to get the web URL for. Returns: The web URL from Cyberbro API - Useful for the user to check the results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
analysis_idYes

Implementation Reference

  • src/mcp_cyberbro/tools/web.py:12-20 (handler)
    The handler function that implements the tool logic. Takes an analysis_id and returns a dict with the web URL constructed from config.cyberbro_url.
    async def get_web_url(analysis_id: str) -> Any:
    """
    Get the web GUI URL for a given analysis ID.
    Args:
        analysis_id: Analysis ID to get the web URL for.
    Returns:
        The web URL from Cyberbro API - Useful for the user to check the results.
    """
    return {"web_url": f"{config.cyberbro_url}/results/{analysis_id}"}
  • src/mcp_cyberbro/tools/web.py:10-20 (registration)
    The registration function that uses @mcp.tool() decorator to register get_web_url as an MCP tool.
    def register_web_tools(mcp: FastMCP, config: CyberbroConfig) -> None:
    @mcp.tool()
    async def get_web_url(analysis_id: str) -> Any:
        """
        Get the web GUI URL for a given analysis ID.
        Args:
            analysis_id: Analysis ID to get the web URL for.
        Returns:
            The web URL from Cyberbro API - Useful for the user to check the results.
        """
        return {"web_url": f"{config.cyberbro_url}/results/{analysis_id}"}
  • src/mcp_cyberbro/server.py:16-16 (registration)
    Registration call site: invoked in create_server() to register the web tools on the MCP server.
    register_web_tools(mcp, config)
  • src/mcp_cyberbro/tools/web.py:7-7 (helper)
    CyberbroConfig provides the config object (cyberbro_url) used to build the web URL.
    from mcp_cyberbro.utils.config import CyberbroConfig

Tool Definition Quality

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Without annotations, the description carries full burden. It only mentions the return value ('web URL from Cyberbro API') but does not disclose read-only nature, authentication needs, or side effects. Behavioral traits are inadequately addressed.

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 concise with two sentences and clearly separated args/returns. It is front-loaded with the core purpose. Minor improvement possible by structuring the return statement.

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?

For a simple tool with one parameter and no output schema, the description is mostly adequate but lacks guidance on when to use vs siblings and does not explain if the URL requires authentication. A more complete description would mention usage context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description adds only a restatement of the parameter purpose ('Analysis ID to get the web URL for'). No format, constraints, or examples are provided, leaving the agent with minimal additional meaning.

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 retrieves a web GUI URL for a given analysis ID, using a specific verb and resource. It distinguishes from siblings like get_analysis_results (raw data) and is_analysis_complete (status check).

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?

No explicit guidance on when to use this tool versus alternatives like get_analysis_results or analyze_observable. The description merely states the function without context for selection.

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/stanfrbd/mcp-cyberbro'

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