Skip to main content
Glama
threat-zone

Threat.Zone MCP Server

by threat-zone

get_my_submissions

Retrieve your malware analysis submissions with pagination to manage and review threat investigation history on Threat.Zone MCP Server.

Instructions

Get user's submissions with pagination.

Args: page: Page number (default: 1) jump: Number of items per page (default: 10)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
jumpNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_my_submissions' MCP tool. It is registered via the @app.tool decorator and fetches the user's submissions with pagination parameters using the shared API client.
    @app.tool
    async def get_my_submissions(page: int = 1, jump: int = 10) -> Dict[str, Any]:
        """
        Get user's submissions with pagination.
        
        Args:
            page: Page number (default: 1)
            jump: Number of items per page (default: 10)
        """
        return await get_client().get(f"/public-api/get/my-submissions/{page}/{jump}")
  • The @app.tool decorator registers the get_my_submissions function as an MCP tool on the FastMCP server instance.
    @app.tool
  • The get_client() helper function used by get_my_submissions to obtain the API client instance for making the HTTP request.
    def get_client():
        """Get or create the API client."""
        global client
        if client is None:
            if not API_KEY:
                raise ThreatZoneError("THREATZONE_API_KEY environment variable is required")
            client = APIClient(API_KEY)
        return client
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 pagination behavior, which is valuable, but doesn't disclose other important traits like authentication requirements, rate limits, error conditions, or what 'user' means in this context (current authenticated user vs. specified user). The description is minimal beyond the pagination hint.

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 extremely concise and well-structured: a clear purpose statement followed by parameter explanations. Every sentence earns its place, with no wasted words. The two-sentence format is front-loaded with the core functionality.

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 that an output schema exists (context signals indicate 'Has output schema: true'), the description doesn't need to explain return values. However, for a tool with 2 parameters and no annotations, the description is minimal—it covers pagination basics but lacks context about authentication, error handling, or sibling tool relationships, making it adequate but with clear gaps.

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

Parameters4/5

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

With 0% schema description coverage, the description fully compensates by explaining both parameters: 'page' as page number with default 1, and 'jump' as items per page with default 10. This adds crucial meaning beyond the bare schema, though it doesn't clarify parameter constraints (e.g., valid ranges) or the relationship between them.

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 with a specific verb ('Get') and resource ('user's submissions'), and mentions pagination as a key feature. However, it doesn't explicitly differentiate from sibling tools like 'get_submission' (singular) or 'get_public_submissions', leaving some ambiguity about scope.

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 provides no guidance on when to use this tool versus alternatives. With siblings like 'get_submission' (singular), 'get_public_submissions', and 'get_submission_status_summary', there's no indication of when this paginated list of user submissions is preferred over other submission-related tools.

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/threat-zone/threatzonemcp'

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