Skip to main content
Glama
threat-zone

Threat.Zone MCP Server

by threat-zone
OverviewSchemaRelated ServersScoreDiscussions
Python

get_submission_varist_results

Retrieve Varist Hybrid Analyzer results for malware analysis submissions using the submission UUID to access detailed threat intelligence and sandbox execution data.

Instructions

Get Varist Hybrid Analyzer results for a specific submission.

Args: uuid: Submission UUID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/threatzone_mcp/server.py:480-488 (handler)
    This is the main handler function for the 'get_submission_varist_results' tool. It is decorated with @app.tool, which registers it as an MCP tool in FastMCP. The function retrieves Varist Hybrid Analyzer results for a given submission UUID by calling the ThreatZone API via the get_client() helper.
    @app.tool
async def get_submission_varist_results(uuid: str) -> Dict[str, Any]:
    """
    Get Varist Hybrid Analyzer results for a specific submission.
    
    Args:
        uuid: Submission UUID
    """
    return await get_client().get(f"/public-api/get/submission/{uuid}/varist-hybrid-analyzer-results")

Tool Definition Quality

C2.9/5.0
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 tool 'gets' results, implying a read-only operation, but doesn't specify whether this requires authentication, has rate limits, returns structured data, or involves pagination. For a tool with no annotation coverage, this leaves significant behavioral gaps unaddressed.

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 concise with two sentences: one stating the purpose and another listing the parameter. It's front-loaded with the main function. There's no wasted text, though the structure is simple without explicit sections beyond 'Args:'.

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 low parameter complexity (1 param with 0% schema coverage), the description is minimally complete. It covers the purpose and parameter meaning but lacks behavioral context and usage guidelines. For a read operation with output schema support, this is adequate but not thorough.

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 parameter semantics: it explains that 'uuid' is a 'Submission UUID', which clarifies the parameter's purpose beyond the schema's generic 'string' type. However, with 0% schema description coverage and only one parameter, this is adequate but not exceptional. It doesn't provide format details (e.g., UUID version) or examples, so it meets the baseline for low 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 'Varist Hybrid Analyzer results for a specific submission', making the purpose understandable. It distinguishes this tool from siblings like 'get_submission' or 'get_submission_status_summary' by specifying the type of results (Varist Hybrid Analyzer). However, it doesn't explicitly contrast with all similar tools (e.g., 'get_submission_indicators'), so it's not a perfect 5.

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 like 'get_submission', 'get_submission_indicators', and 'get_submission_iocs', there's no indication of what makes this tool unique or when it should be preferred. The only implied context is needing Varist Hybrid Analyzer results, but no explicit usage rules are given.

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