Skip to main content
Glama
threat-zone

Threat.Zone MCP Server

by threat-zone

get_metafields

Retrieve available metafields to configure malware analysis scans for files and URLs using Threat.Zone's security tools.

Instructions

Get available metafields for scan configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_metafields' tool. It is decorated with @app.tool, which registers it as an MCP tool. The function fetches available metafields from the ThreatZone API using the shared API client.
    @app.tool
    async def get_metafields() -> Dict[str, Any]:
        """Get available metafields for scan configuration."""
        return await get_client().get("/public-api/constants/metafields")
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 implies a read operation ('Get') but doesn't disclose behavioral traits such as authentication needs, rate limits, or what 'available' means (e.g., all metafields, user-specific). The description is minimal, leaving key operational details unspecified.

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 a single, efficient sentence with no wasted words. It's front-loaded and appropriately sized for a simple tool, making it easy to parse quickly without redundancy.

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 0 parameters, 100% schema coverage, and an output schema exists, the description is minimally adequate. However, as a tool with no annotations and siblings like 'get_sample_metafield', it should clarify scope or usage to be fully complete, leaving some contextual gaps.

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, which is appropriate here. Baseline is 4 since no parameters exist, and it doesn't compensate unnecessarily.

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 states the tool's purpose as 'Get available metafields for scan configuration', which is clear but vague. It specifies the verb 'Get' and resource 'metafields', but lacks detail on what metafields are or their scope. It doesn't distinguish from siblings like 'get_sample_metafield', leaving ambiguity.

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_sample_metafield' and 'get_submission_config_extractor', the description doesn't explain if this is for general metadata, specific scans, or configuration setup, offering no context for selection.

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