Skip to main content
Glama
threat-zone

Threat.Zone MCP Server

by threat-zone

get_submission

Retrieve detailed malware analysis results for a specific submission using its unique identifier, enabling threat investigation and security assessment.

Instructions

Get submission details by UUID.

Args: uuid: Submission UUID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_submission' MCP tool. It is registered via the @app.tool decorator in FastMCP and retrieves submission details from the ThreatZone API endpoint using the provided UUID.
    async def get_submission(uuid: str) -> Dict[str, Any]:
        """
        Get submission details by UUID.
        
        Args:
            uuid: Submission UUID
        """
        return await get_client().get(f"/public-api/get/submission/{uuid}")
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 of behavioral disclosure. It states this is a 'Get' operation, implying read-only behavior, but doesn't specify if it requires authentication, rate limits, error handling, or what 'details' include. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

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 and front-loaded: the first sentence states the purpose clearly. The 'Args' section is structured but could be integrated more smoothly. There's no wasted text, though it might benefit from a bit more detail given the lack of annotations.

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), no annotations, and a simple parameter, the description is minimally adequate. However, it doesn't address key contextual aspects like how this tool differs from siblings or behavioral traits, leaving the agent to guess in a crowded toolset.

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?

The description adds minimal semantics beyond the input schema: it clarifies that 'uuid' is a 'Submission UUID,' which provides context not in the schema (which has 0% description coverage). However, it doesn't explain the UUID format, source, or validation rules. With one parameter and low schema coverage, this offers basic but incomplete compensation.

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: 'Get submission details by UUID.' It specifies the verb ('Get') and resource ('submission details'), making the action clear. However, it doesn't differentiate from sibling tools like 'get_my_submissions' or 'get_public_submissions' that also retrieve submissions, leaving some ambiguity about when to use this specific tool.

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_my_submissions' and 'get_public_submissions' that likely retrieve submissions in different ways, there's no mention of context, prerequisites, or exclusions. The agent must infer usage from 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/threat-zone/threatzonemcp'

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