Skip to main content
Glama

BRAINIAC Malware & File Threat Intelligence

Extract file behaviour indicators

file-security_file-behavior-indicator-extract

Extract suspicious behaviour indicators from caller-supplied analysis reports/text using local static pattern matching. Files are never executed. Absence of matches is not a malware-free verdict. Price $0.04 USDC. POST /api/v1/file-security/file-behavior-indicator-extract. 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_file-behavior-indicator-extract"
  }
}

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.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that files are never executed, that matching is local and static, the $0.04 USDC cost, and that unpaid calls return 402 without running. It leaves out rate limits and, with no output schema, says nothing about the shape or confidence of returned indicators.

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?

Five tight sentences, front-loaded with purpose and safety, followed by the caveat and the payment/endpoint facts. The endpoint path is marginal value for an agent, but nothing is filler and the important constraint (no execution, 402 on unpaid) is prominent.

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?

It covers purpose, safety, cost, and the key interpretation caveat for a paid endpoint, which is substantial. Yet for a tool with ten parameters, nested file objects, no annotations, and no output schema, the absence of any parameter guidance or return-value description leaves an agent guessing at invocation details.

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?

Ten parameters with 0% schema description coverage and no help from the description, which never mentions text, csv, json, reports, files, artifacts, asOf, maxArchiveDepth, or maxInflateBytes. The relationship between the overlapping file/files/artifacts containers and the archive-inflation limits is entirely undocumented, which is a serious gap given the nested object structure.

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 ('Extract suspicious behaviour indicators') plus the input domain ('caller-supplied analysis reports/text') and the method ('local static pattern matching'), which separates it from execution-based or reputation-based siblings. It stops short of naming a distinct sibling such as malware-indicator-extract, so the boundary with that tool must be inferred.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It makes clear the caller must supply the content to scan and adds a genuine interpretation rule ('Absence of matches is not a malware-free verdict'), which is real usage guidance. However, there is no explicit when-to-use versus the closely named malware-indicator-extract or suspicious-script-pattern-detect siblings, and no statement of what input combinations are valid.

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