Skip to main content
Glama
threat-zone

Threat.Zone MCP Server

by threat-zone

get_submission_indicators

Retrieve threat indicators from a malware analysis submission to identify malicious patterns and behaviors for security investigation.

Instructions

Get all indicators 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 decorated with @app.tool, which registers and implements the get_submission_indicators tool. It fetches indicators for a submission UUID from the ThreatZone API using the get_client() helper.
    @app.tool
    async def get_submission_indicators(uuid: str) -> Dict[str, Any]:
        """
        Get all indicators for a specific submission.
        
        Args:
            uuid: Submission UUID
        """
        return await get_client().get(f"/public-api/get/submission/{uuid}/indicators")
  • The @app.tool decorator registers the get_submission_indicators function as an MCP tool.
    @app.tool
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 is to 'Get' data, implying a read-only operation, but does not specify permissions, rate limits, response format, or error handling. This leaves significant gaps in understanding how the tool behaves beyond its basic function.

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 with the main purpose in the first sentence, followed by parameter details. It avoids unnecessary words, but the structure could be improved by integrating parameter information more seamlessly rather than as a separate 'Args' section.

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 simplicity (one parameter) and the presence of an output schema, the description is minimally complete. However, it lacks context on data scope, relationships to sibling tools, and behavioral traits, which are important for effective use in a server with many similar tools.

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 by naming the parameter 'uuid' and specifying it as a 'Submission UUID', which clarifies its purpose. However, with 0% schema description coverage and only one parameter, this provides basic but insufficient detail, such as format or constraints, resulting in an adequate baseline score.

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 indicators for a specific submission', making the purpose explicit. However, it does not differentiate from sibling tools like 'get_submission_iocs' or 'get_submission_artifacts', which might retrieve similar or overlapping data, leaving some ambiguity in 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, such as other 'get_submission_*' siblings that might retrieve related data. It lacks context on prerequisites, exclusions, or specific use cases, offering only basic parameter information without comparative advice.

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