Skip to main content
Glama

BRAINIAC Malware & File Threat Intelligence

Detect suspicious script patterns

file-security_suspicious-script-pattern-detect

Analyze caller-supplied scripts for suspicious static patterns (encoded commands, download cradles, obfuscation). Scripts are never executed. Price $0.04 USDC. POST /api/v1/file-security/suspicious-script-pattern-detect. 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_suspicious-script-pattern-detect"
  }
}

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
Behavior3/5

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

With no annotations provided, the description carries the full burden, and it does disclose two important behaviors: scripts are never executed (safe static analysis) and unpaid calls return 402 without running. However, it says nothing about what the analysis returns, whether results are cached, how long large batches take, or what limits apply to the archive/inflate parameters.

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?

Front-loaded with the core purpose and the critical 'never executed' safety note, then pricing and endpoint. Four short sentences with little waste, though the raw endpoint path adds marginal value for an agent compared to the rest.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 10 parameters, nested objects, no annotations, and no output schema, the description is thin. It never describes the response shape (findings, scores, matched patterns) nor which of the many input channels to use, leaving the agent to guess both inputs and outputs.

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 including nested file objects, yet the description adds no parameter meaning at all. It does not explain that script content can arrive via text, csv, json, file.fileBase64, files, artifacts, or reports, nor what maxArchiveDepth and maxInflateBytes control.

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

Purpose5/5

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

States a specific verb ('Analyze'), a specific resource ('caller-supplied scripts'), and concrete detection targets (encoded commands, download cradles, obfuscation). This distinguishes it clearly from sibling detectors like archive-payload, macro-document, and executable-metadata analysis without needing to name them.

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?

Usage is implied: you supply script content and get a static pattern verdict. But there is no explicit when-to-use vs. when-not guidance, no statement about which input parameter to choose for a given script source, and no mention of alternatives such as the behavior-indicator or malware-indicator extractor siblings.

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