Skip to main content
Glama
threat-zone

Threat.Zone MCP Server

by threat-zone

get_submission_udp

Retrieve UDP requests and packets for a specific malware analysis submission to analyze network traffic patterns and identify malicious communication.

Instructions

Get all UDP requests and packets for a specific submission.

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_udp' tool. It retrieves UDP requests and packets for a given submission UUID by calling the ThreatZone API endpoint `/public-api/get/submission/{uuid}/udp`. Registered via @app.tool decorator.
    @app.tool
    async def get_submission_udp(uuid: str) -> Dict[str, Any]:
        """
        Get all UDP requests and packets for a specific submission.
        
        Args:
            uuid: Submission UUID
        """
        return await get_client().get(f"/public-api/get/submission/{uuid}/udp")
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'gets' data, implying a read-only operation, but doesn't specify permissions, rate limits, response format, or potential errors. This is inadequate for a tool with an output schema, as it lacks context on what behavior to expect beyond basic retrieval.

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 front-loaded with the core purpose in the first sentence, followed by parameter details. It's appropriately sized with no wasted words, though the structure could be slightly improved by integrating the Args more seamlessly.

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's complexity (retrieving UDP data for a submission), no annotations, and an output schema exists, the description is minimally adequate. It covers the basic purpose and parameter but lacks behavioral context and usage guidelines, making it incomplete for optimal agent operation.

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 includes an 'Args' section that explains the 'uuid' parameter as 'Submission UUID', adding meaning beyond the schema's 0% coverage. However, it doesn't provide format details, examples, or constraints, leaving gaps in understanding despite compensating somewhat for the low schema coverage.

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 verb 'Get' and the resource 'all UDP requests and packets for a specific submission', making the purpose understandable. It distinguishes from siblings like 'get_submission_tcp' by specifying UDP, but doesn't explicitly differentiate from other submission-related tools beyond that 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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context for usage, or comparisons with sibling tools like 'get_submission' or 'get_submission_status_summary', leaving the agent without direction on 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/threat-zone/threatzonemcp'

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