Skip to main content
Glama
threat-zone

Threat.Zone MCP Server

by threat-zone

get_submission_yara_rules

Retrieve YARA rules matched during malware analysis to identify threats and understand detection patterns for a specific submission.

Instructions

Get all matched YARA rules 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, implementing the tool logic by fetching matched YARA rules from the ThreatZone API endpoint for the given submission UUID.
    @app.tool
    async def get_submission_yara_rules(uuid: str) -> Dict[str, Any]:
        """
        Get all matched YARA rules for a specific submission.
        
        Args:
            uuid: Submission UUID
        """
        return await get_client().get(f"/public-api/get/submission/{uuid}/matched-yara-rules")
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. It states the action is to 'Get' data, implying a read-only operation, but doesn't disclose behavioral traits such as authentication needs, rate limits, error handling, or what 'matched YARA rules' entails (e.g., format, scope). This is a significant gap for a tool with no annotation coverage.

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 a brief Args section. It's efficient with zero waste, though the structure is simple and could be more polished for clarity.

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, the description is minimally complete. It covers the basic purpose and parameter intent but lacks usage guidelines and behavioral details, making it adequate but with clear gaps for effective agent use.

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 beyond the input schema: it specifies that 'uuid' is a 'Submission UUID,' which clarifies the parameter's purpose. However, with 0% schema description coverage and only one parameter, this is adequate but not comprehensive—it doesn't explain format or constraints beyond what's implied.

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 matched YARA rules for a specific submission,' making the purpose explicit. However, it doesn't distinguish this tool from sibling tools like 'get_submission_indicators' or 'get_submission_iocs,' which might also retrieve submission-related data, so it misses full differentiation.

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' or 'get_submission_indicators,' there's no indication of context, prerequisites, or exclusions, leaving the agent to guess based on tool 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