Skip to main content
Glama

BRAINIAC Malware & File Threat Intelligence

Cluster malware artifacts

file-security_malware-artifact-cluster

Group caller-supplied files/artifacts by identical hashes and structural similarity (magic/extension/size). Clustering is not family attribution or confirmed malware. Price $0.04 USDC. POST /api/v1/file-security/malware-artifact-cluster. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "file-security_malware-artifact-cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
filesNo
reportsNo
artifactsNo
maxArchiveDepthNo
maxInflateBytesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral burden and discloses several important traits: caller-supplied inputs, the basis for clustering, the limitation that results are not family attribution or confirmed malware, the price, the endpoint, and that unpaid calls return 402 and do not run. This is strong context for a paid analysis endpoint. It does not address data retention, side effects, or return shape, so it is not fully comprehensive.

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 compact and front-loaded: purpose first, then the key interpretive caveat, then pricing and endpoint details. Every sentence carries operational or interpretive value, including the 402 behavior. There is no unnecessary wording.

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?

For a complex 10-parameter tool with nested objects and no annotations, the description covers purpose, caveats, pricing, and payment failure behavior well. However, it leaves a substantial gap around how to choose among the multiple input modes and how the nested file/artifact/report structures should be used. It is adequate for deciding what the tool does, but not complete for invoking it confidently.

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

Parameters2/5

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

The schema has 10 parameters and 0% description coverage, so the description needs to explain input selection and nested object semantics. It only loosely references hashes, magic, extension, and size, without mapping these to csv, json, text, file, files, artifacts, reports, maxArchiveDepth, or maxInflateBytes. It adds very little meaning beyond the bare property names.

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 states a specific verb and resource: group caller-supplied files/artifacts by identical hashes and structural similarity (magic/extension/size). It also clarifies that clustering is not family attribution or confirmed malware, which prevents a common misinterpretation. It does not explicitly differentiate itself from every sibling, so it falls short of a 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 implies that the tool is for grouping similar or identical artifacts, but it gives no explicit when-to-use or when-not-to-use guidance relative to alternatives. The caveat about family attribution clarifies output interpretation, not tool selection. An agent would need to infer that this is the grouping tool rather than an indicator-extraction or mismatch-detection tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources