Skip to main content
Glama

threat_reputation

Aggregates VirusTotal, OTX, GreyNoise, Tor, DNS blocklists, Shodan InternetDB, and OpenPhish signals to return a one-shot reputation verdict for IPs, domains, URLs, or file hashes.

Instructions

One-shot reputation verdict for an IP, domain, URL or file hash.

Aggregates VirusTotal, OTX, GreyNoise, Tor exit status, DNS blocklists, Shodan InternetDB and OpenPhish where applicable. Requires VIRUSTOTAL_API_KEY; the other sources are keyless or optional.

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": {
      "target": "<target>"
    },
    "name": "threat_reputation"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does deliver real behavioral context: the tool fans out to seven named sources and requires VIRUSTOTAL_API_KEY while the rest are keyless or optional, which tells the agent about auth prerequisites and graceful degradation. It says nothing about rate limits, latency from multi-source fan-out, or whether failures of individual sources surface in the result.

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?

The verdict purpose leads, followed by sources, then the auth requirement — a sensible front-loading with no filler sentences. Hard line breaks inside the source list fragment sentences unnecessarily and slightly hurt scannability, but nothing is wasteful.

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?

For a single-parameter aggregator with no annotations and no output schema, the definition covers inputs, sources, and key requirements adequately. The notable omission is any indication of what the 'verdict' looks like (score, per-source breakdown, verdict label), which matters more than usual because no output schema exists to describe the return value.

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

Parameters4/5

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

Schema coverage is 0% and the only schema hint is the title 'Target', but the description compensates by defining the domain of valid values as IP, domain, URL or file hash. That is the critical semantic the schema lacks; only the exact accepted input formats (e.g. hash length, URL scheme requirements) remain unspecified.

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 concrete verb and resource ('one-shot reputation verdict') and enumerates the accepted input types (IP, domain, URL, file hash), which is far more specific than the bare tool name. It stops short of distinguishing itself from related siblings such as asn_lookup, dns_lookup or deep_osint, so an agent must infer the boundary from names alone.

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?

'One-shot' implies a single consolidated check rather than a deep pivot, and 'where applicable' hints that source coverage varies by indicator type. However, no explicit when-to-use vs. when-to-use-an-alternative guidance is given, and there is no statement of when this tool is the wrong choice.

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