Skip to main content
Glama
threat-zone

Threat.Zone MCP Server

by threat-zone

get_submission_iocs

Extract Indicators of Compromise (IOCs) from a specific malware analysis submission using its UUID to identify threat artifacts and malicious activity patterns.

Instructions

Get all Indicators of Compromise for a specific submission.

Args: uuid: Submission UUID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function decorated with @app.tool, which registers and implements the get_submission_iocs tool. It takes a submission UUID and retrieves IOCs via the ThreatZone API client.
    @app.tool
    async def get_submission_iocs(uuid: str) -> Dict[str, Any]:
        """
        Get all Indicators of Compromise for a specific submission.
        
        Args:
            uuid: Submission UUID
        """
        return await get_client().get(f"/public-api/get/submission/{uuid}/iocs")
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 the action ('Get') but lacks details on permissions, rate limits, response format, or error handling. This is inadequate for a tool with an output schema, as it doesn't prepare the agent for what to expect beyond basic functionality.

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 brief and front-loaded with the main purpose, followed by parameter details. It avoids unnecessary words, but the 'Args' section could be integrated more seamlessly, and it lacks a concluding note on output or usage, slightly reducing efficiency.

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, the description doesn't need to explain return values, which helps. However, with no annotations, 0% schema description coverage, and many sibling tools, it falls short by not addressing behavioral aspects or usage context, making it only minimally adequate.

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 documents the single parameter 'uuid' as 'Submission UUID', adding meaning beyond the input schema, which has 0% description coverage. However, it doesn't provide examples, format details (e.g., UUID version), or constraints, so it only partially compensates for the schema gap.

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 resource ('Indicators of Compromise for a specific submission'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_submission_indicators', which might serve a similar or overlapping function, preventing a perfect score.

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 many sibling tools (e.g., 'get_submission_indicators', 'get_submission_artifacts'), there is no indication of context, prerequisites, or exclusions, leaving the agent to infer usage based on names 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