Skip to main content
Glama
threat-zone

Threat.Zone MCP Server

by threat-zone

get_statuses

Retrieve analysis status updates for submitted malware samples or URLs to monitor threat investigation progress within Threat.Zone's security platform.

Instructions

Get submission statuses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get_statuses' tool. It is decorated with @app.tool, which registers it as an MCP tool. The function retrieves submission statuses from the ThreatZone API using the get_client() helper.
    @app.tool
    async def get_statuses() -> Dict[str, Any]:
        """Get submission statuses."""
        return await get_client().get("/public-api/constants/statuses")
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 only states the action ('Get') without disclosing behavioral traits like whether it's read-only, if it requires authentication, rate limits, or what the output entails. This is inadequate 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with a single sentence 'Get submission statuses.' It's front-loaded and wastes no words, making it efficient for quick understanding, though this brevity contributes to gaps in other dimensions.

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 0 parameters, 100% schema coverage, and an output schema exists, the description is minimally complete. However, with no annotations and multiple sibling tools, it lacks context on usage and behavior, making it only adequate but with clear gaps in guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, but since there are no params, this is acceptable, aligning with the baseline for zero parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get submission statuses' clearly states the verb ('Get') and resource ('submission statuses'), but it's vague about scope—it doesn't specify if this retrieves all statuses, a filtered set, or a summary. It distinguishes from siblings like 'get_submission_status_summary' by not mentioning 'summary', but the distinction is minimal and lacks detail.

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 siblings like 'get_submission_status_summary' and 'get_my_submissions', the description doesn't indicate if this is for all submissions, specific contexts, or how it differs, 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