Skip to main content
Glama
joesecurity

JoeSandboxMCP

Official
by joesecurity

get_list_of_recent_analyses

Retrieve summaries of recent malware analyses from Joe Sandbox Cloud, including detection scores, file details, and submission metadata for follow-up investigation.

Instructions

List recent analyses submitted by the user.

This tool returns a summary of the most recent sandbox analyses performed in the current account. Each entry includes the submission ID and a minimal set of metadata useful for follow-up actions such as downloading artifacts or examining behavior.

By default, the tool returns the latest 20 analyses. You can override the `limit` parameter to retrieve more or fewer entries.

For each analysis, the following fields are returned:
    - webid: Unique submission identifier.
    - time: Timestamp of when the analysis was submitted.
    - filename: Original submitted filename or URL.
    - sha256: SHA-256 hash of the submitted object.
    - score: Final detection score assigned by the sandbox.
    - detection: Verdict (e.g., clean, suspicious, malicious).
    - classification: Malware family or type (if available).
    - threatname: Named threat label (e.g., campaign or actor), if detected.
    - systems: List of sandbox systems the sample was run on.
    - num_runs: Total number of sandbox executions (runs) for this submission.

Args:
    limit (optional, default = 20): The number of most recent analyses to return.

Returns:
    A list of dictionaries summarizing each recent analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Implementation Reference

  • The @mcp.tool()-decorated async handler function implementing the tool logic. It wraps the synchronous core helper in asyncio.to_thread for async compatibility.
    @mcp.tool()
    async def get_list_of_recent_analyses(limit: int = 20) -> List[Dict[str, Any]]:
        """
        List recent analyses submitted by the user.
    
        This tool returns a summary of the most recent sandbox analyses performed in the current account. Each entry includes the submission ID and a minimal set of metadata useful for follow-up actions such as downloading artifacts or examining behavior.
    
        By default, the tool returns the latest 20 analyses. You can override the `limit` parameter to retrieve more or fewer entries.
    
        For each analysis, the following fields are returned:
            - webid: Unique submission identifier.
            - time: Timestamp of when the analysis was submitted.
            - filename: Original submitted filename or URL.
            - sha256: SHA-256 hash of the submitted object.
            - score: Final detection score assigned by the sandbox.
            - detection: Verdict (e.g., clean, suspicious, malicious).
            - classification: Malware family or type (if available).
            - threatname: Named threat label (e.g., campaign or actor), if detected.
            - systems: List of sandbox systems the sample was run on.
            - num_runs: Total number of sandbox executions (runs) for this submission.
    
        Args:
            limit (optional, default = 20): The number of most recent analyses to return.
    
        Returns:
            A list of dictionaries summarizing each recent analysis.
        """
        return await asyncio.to_thread(list_recent_analyses, limit)
  • The core synchronous helper function that performs the actual API calls to list recent analyses using Joe Sandbox client, collecting metadata up to the specified limit.
    def list_recent_analyses(limit: int = 20) -> List[Dict[str, Any]]:
        jbx_client = get_client()
        results = []
    
        for each in jbx_client.analysis_list_paged():
            info = jbx_client.analysis_info(webid=each["webid"])
    
            systems = list({run.get("system") for run in info.get("runs", []) if run.get("system")})
            num_runs = len(info.get("runs", []))
    
            results.append({
                "webid": info.get("webid"),
                "time": info.get("time"),
                "filename": info.get("filename"),
                "sha256": info.get("sha256"),
                "score": info.get("score"),
                "detection": info.get("detection"),
                "classification": info.get("classification"),
                "threatname": info.get("threatname"),
                "systems": systems,
                "num_runs": num_runs,
            })
    
            if len(results) >= limit:
                break
    
        return results
  • jbxmcp/server.py:19-19 (registration)
    Import of the tools module in the server.py, which executes the @mcp.tool() decorators on all tool functions including get_list_of_recent_analyses, registering them with the FastMCP instance.
    import jbxmcp.tools as tools
Behavior4/5

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

With no annotations provided, the description carries full burden and does well: it discloses the default behavior (returns latest 20 analyses), return format (list of dictionaries with specific fields), and purpose (summary for follow-up actions). It doesn't mention rate limits, authentication needs, or pagination behavior, leaving some gaps.

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?

Well-structured and appropriately sized: front-loaded with core purpose, followed by behavioral details, parameter explanation, and return format. Every sentence adds value—no redundancy or fluff. The bulleted list of return fields is efficient for clarity.

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?

For a tool with no annotations, no output schema, and 1 parameter with 0% schema coverage, the description is quite complete: it covers purpose, behavior, parameter semantics, and return structure. However, it lacks details on error handling, authentication, or rate limits, which could be relevant given the sibling tools suggest a security analysis context.

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

Parameters5/5

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

The schema has 0% description coverage (only title 'Limit'), so the description must compensate fully. It clearly explains the 'limit' parameter's purpose ('override to retrieve more or fewer entries'), default value (20), and effect ('number of most recent analyses to return'), adding significant meaning beyond the bare schema.

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's purpose with specific verb ('List') and resource ('recent analyses submitted by the user'), distinguishing it from siblings like 'get_analysis_info' (detailed single analysis) or 'search_analysis' (filtered search). It explicitly mentions 'sandbox analyses' and 'current account' context.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool ('summary of the most recent sandbox analyses') and implies usage for follow-up actions like downloading artifacts. However, it doesn't explicitly state when NOT to use it or name specific alternatives among the sibling tools, though the distinction is reasonably inferable.

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/joesecurity/joesandboxMCP'

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