Skip to main content
Glama
Sign In
Forensics Utils MCP Server

Forensics Utils MCP Server

by jus1-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

vt_get_domain_report_tool

Retrieve a VirusTotal domain report with WHOIS, DNS, SSL certificates, reputation score, and related files/URLs to assess domain security.

Instructions

Get VirusTotal intelligence report for a domain.

Includes: WHOIS data, DNS records, SSL certificates, reputation score, and related files/URLs.

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": {
      "domain": "<domain>"
    },
    "name": "vt_get_domain_report_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe domain name (e.g., "example.com")

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description is the sole source of behavioral transparency. It implies a read-only operation ('Get') and lists report contents, but does not mention authentication needs, rate limits, or error/edge-case behavior. It provides some useful context but is not rich.

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 concise: two sentences, front-loaded with the purpose, and the second sentence lists useful included data. No wasted words or redundancy.

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

Completeness4/5

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

An output schema is present, so return values are covered. The description effectively summarizes the report content and the tool's simple single-parameter interface. It is adequately complete for an agent to invoke it correctly.

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?

The schema already provides 100% coverage with a clear description for the 'domain' parameter. The tool description adds no additional parameter semantics beyond what the schema gives, so the baseline score of 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?

The description clearly states the verb 'Get' and the specific resource 'VirusTotal intelligence report for a domain'. It lists concrete included data (WHOIS, DNS, SSL, reputation, related files/URLs), which distinguishes it from sibling tools that target files, URLs, or IPs.

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

Usage Guidelines4/5

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

The description clearly indicates use for domains, giving enough context for an agent to select it when domain intelligence is needed. It does not explicitly compare with alternatives like vt_get_url_report_tool, but the domain-specific scope is unambiguous.

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