Skip to main content
Glama
Sign In
Forensics Utils MCP Server

Forensics Utils MCP Server

by jus1-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

vt_get_file_behavior_tool

Retrieve the behavior summary of a file analyzed in VirusTotal's sandbox using its SHA256 hash, aiding forensic investigations.

Instructions

Get behavior summary for a file analyzed in VirusTotal's sandbox.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file_hash": "<file_hash>"
    },
    "name": "vt_get_file_behavior_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_hashYesSHA256 hash of the file

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description is the sole source of behavioral info. It clearly indicates a read operation ('Get') but does not disclose prerequisites (e.g., whether the file must already be analyzed) or error conditions. This is adequate but minimal.

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?

Single sentence, front-loaded with the verb, no unnecessary words.

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 simple one-parameter tool with output schema, the description is functional but lacks guidance on when to choose this over sibling tools and does not mention any prerequisite about prior analysis. Output schema covers return values.

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

Parameters3/5

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

Schema covers 100% of parameters with a clear description for file_hash. The tool description adds no parameter-level detail; baseline 3 applies.

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?

Description uses specific verb 'Get' with resource 'behavior summary' and scope 'file analyzed in VirusTotal's sandbox'. This clearly distinguishes from vt_get_file_report_tool which likely provides the full report.

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 on when to use this tool versus alternative VT tools like vt_get_file_report_tool. The description only states what it does, leaving the agent to infer selection.

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

Deploy Server

Other Tools