Skip to main content
Glama

otx_domain

Retrieve AlienVault OTX threat intelligence for a domain, including pulses, malware associations, hosted URLs, and validation, to support authorized OSINT investigations.

Instructions

AlienVault OTX threat profile for a domain: pulses, malware, hosted URLs, validation.

Uses the OTX DirectConnect API. A key (OTX_API_KEY or keys.json) raises limits; without one, OTX may return 403/429. Passive-DNS is intentionally skipped because OTX frequently returns 504 for it.

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": "otx_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so well: it names the upstream API, states that an OTX_API_KEY/keys.json raises limits, warns that unauthenticated calls may return 403/429, and explains that passive-DNS is deliberately absent to avoid 504s. It stops short of describing return shape or overall rate limits.

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?

Four short sentences, purpose front-loaded, followed by the API and operational caveats. No filler, though the line breaks fragment what is logically one paragraph.

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 two-parameter read-only lookup with no output schema, the description covers content coverage, authentication prerequisites, and a known data gap. The only meaningful omission is the undocumented `limit` parameter's behavior.

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% for the two parameters, so the description must compensate and does not: neither the meaning or units of `limit` (schema default 50) nor the expected format of `domain` is addressed anywhere.

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 resource and provider: an AlienVault OTX threat profile for a domain, enumerating the content returned (pulses, malware, hosted URLs, validation). It does not name or distinguish itself from sibling domain tools such as domain_whois or recon_domain, which keeps it short of a 5.

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 by the content list (domain threat intelligence), and one scope exclusion is given explicitly (passive-DNS skipped due to 504s). There is no statement of when to prefer this over the sibling domain lookups, so the agent must infer selection.

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