Skip to main content
Glama

BRAINIAC Malware & File Threat Intelligence

Extract malware indicators

file-security_malware-indicator-extract

Extract IPs, domains, URLs, hashes, and emails from caller-supplied files/reports using local static parsing. Extracted strings are not live threat-intel verdicts. Price $0.04 USDC. POST /api/v1/file-security/malware-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_malware-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.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 disclosure burden and does well: it declares static local parsing (no external lookups), warns the output is not a verdict, gives the cost ($0.04 USDC), the transport (POST /api/v1/file-security/malware-indicator-extract), and that unpaid calls return 402 without running. Missing pieces are the response shape and how archive/inflate limits affect processing, but the safety-and-billing profile is otherwise clear.

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?

Three tight sentences with the core capability front-loaded, followed by the interpretative caveat, then cost/transport/failure behavior. Every sentence adds distinct information and none is padding.

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 10-parameter tool with nested objects, no annotations, and no output schema, the definition covers purpose, cost, and payment failure well but leaves the input model (multiple alternative payload shapes, archive depth/inflate caps) undocumented. An agent could call it, but only by guessing which input field to populate.

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?

Schema description coverage is 0% across 10 parameters, so the description must compensate and largely does not. 'Caller-supplied files/reports' hints at the file/files/reports/text inputs, but csv, json, asOf, artifacts, maxArchiveDepth, and maxInflateBytes get no mention, and the mutual exclusivity of the input variants is never stated.

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?

States a specific verb and resource set — 'Extract IPs, domains, URLs, hashes, and emails' from 'caller-supplied files/reports' — plus the mechanism ('local static parsing'). An agent knows exactly what comes out, but nothing in the text distinguishes it from the close sibling file-security_file-behavior-indicator-extract, so the differentiation is left implicit.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative, despite a dense sibling family (behavior-indicator-extract, suspicious-script-pattern-detect, archive-payload-risk-detect). The only routing-adjacent statement is the negative scope 'Extracted strings are not live threat-intel verdicts', which clarifies output meaning rather than tool selection.

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