Skip to main content
Glama
threat-zone

Threat.Zone MCP Server

by threat-zone

get_public_submissions

Retrieve publicly available malware analysis submissions with pagination controls to browse and access threat intelligence data from the Threat.Zone platform.

Instructions

Get public 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

  • Handler function for the get_public_submissions tool. Decorated with @app.tool, which registers it in the FastMCP server. Fetches paginated public submissions from the ThreatZone API.
    @app.tool
    async def get_public_submissions(page: int = 1, jump: int = 10) -> Dict[str, Any]:
        """
        Get public 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/public-submissions/{page}/{jump}")
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 pagination behavior, which is valuable, but doesn't disclose other important traits like authentication requirements, rate limits, error conditions, or what constitutes a 'public submission'. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 two sentences: a purpose statement followed by parameter documentation. It's front-loaded with the core functionality. The parameter documentation could be slightly more integrated, but overall there's minimal waste.

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 the tool has an output schema (which handles return values), 2 parameters with 0% schema coverage, and no annotations, the description does an adequate job covering basics. However, for a tool that presumably returns sensitive data (submissions), it should better explain what 'public' means and any access constraints.

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?

With 0% schema description coverage, the description compensates by documenting both parameters (page and jump) with their defaults and basic semantics. However, it doesn't explain parameter constraints (e.g., valid ranges), the relationship between parameters, or what 'jump' means beyond 'items per page' (e.g., maximum values).

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 as 'Get public submissions with pagination', which is a specific verb+resource combination. It distinguishes from siblings like 'get_my_submissions' (personal vs public) and 'get_submission' (single vs multiple). However, it doesn't explicitly mention what 'public submissions' are in this context.

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 guidance is provided about when to use this tool versus alternatives. While the name suggests it retrieves public submissions (unlike 'get_my_submissions'), the description doesn't explicitly state this distinction or mention other sibling tools like 'search_by_hash' for different querying needs.

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