Skip to main content
Glama
threat-zone

Threat.Zone MCP Server

by threat-zone

get_submission_config_extractor

Extract configuration data from malware submissions to analyze threat behavior and identify attack patterns in Threat.Zone's security platform.

Instructions

Get all extracted configurations 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 tool handler function, registered via @app.tool decorator, that fetches the config extractor results for a given submission UUID from the ThreatZone API endpoint.
    @app.tool
    async def get_submission_config_extractor(uuid: str) -> Dict[str, Any]:
        """
        Get all extracted configurations for a specific submission.
        
        Args:
            uuid: Submission UUID
        """
        return await get_client().get(f"/public-api/get/submission/{uuid}/config-extractor-results")
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states what the tool does but doesn't disclose behavioral traits like whether this is a read-only operation, what format the configurations are returned in, potential rate limits, or authentication requirements. The description is minimal and lacks operational context.

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 documentation. There's no wasted text, though the structure is simple with just two sentences. It could be more polished but efficiently conveys core information.

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 reduces need to describe return values) but no annotations and minimal parameter coverage, the description is adequate but has clear gaps. It covers the basic purpose and parameter but lacks usage context and behavioral details, making it minimally complete.

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 the parameter 'uuid' and specifies it's a 'Submission UUID', which provides basic semantics. However, with 0% schema description coverage and only one parameter documented, this is the minimum viable baseline. It doesn't elaborate on UUID format, validation, or examples.

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 'all extracted configurations for a specific submission', making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like get_submission or get_submission_artifacts, which appear to retrieve different aspects of submissions.

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. With many sibling tools starting with 'get_submission_', there's no indication of what makes this one unique or when it should be chosen over others like get_submission or get_submission_artifacts.

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