Skip to main content
Glama

BRAINIAC Threat Intelligence & Public Signals

Analyze domain threat history

threat-intelligence_domain-threat-history
Read-onlyIdempotent

Analyze publicly accessible domain history and DNS/RDAP context from caller fields and optional key-free public lookups. History attributes alone are not malice. Price $0.04 USDC. POST /api/v1/threat-intelligence/domain-threat-history. An unpaid call returns the x402 payment terms and does 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": "threat-intelligence_domain-threat-history"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNocsv, string, length 0 to 200000. Optional.
asOfNoasOf, string, length 0 to 40. Optional.
fileNofile, object. Optional.
jsonNojson, string, length 0 to 200000. Optional.
textNotext, string, length 0 to 200000. Optional.
feedsNofeeds, array. Optional.
filesNofiles, array. Optional.
brandsNobrands, array. Optional.
domainsNodomains, array. Optional.
servicesNoservices, array. Optional.
fetchRdapNofetchRdap, boolean. Optional.
publicDnsNopublicDns, boolean. Optional.
staleDaysNostaleDays, number, from 1 to 365. Optional.
candidatesNocandidates, array. Optional.
crtShQueryNocrtShQuery, string, length 0 to 253. Optional.
fetchCrtShNofetchCrtSh, boolean. Optional.
indicatorsNoindicators, array. Optional.
certificatesNocertificates, array. Optional.
fetchCisaKevNofetchCisaKev, boolean. Optional.
fetchOpenPhishNofetchOpenPhish, boolean. Optional.
fetchPhishTankNofetchPhishTank, boolean. Optional.

Output Schema

NameRequiredDescriptionDefault
itemsNoitems. Array.
statusNostatus. String.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
itemCountNoitemCount. Number.
limitationsNolimitations. Array.
apiKeyRequiredNoapiKeyRequired. Boolean.
sourceStatusesNosourceStatuses. Array.
paidProviderUsedNopaidProviderUsed. Boolean.
publicDnsQueriedNopublicDnsQueried. Boolean.
publicFetchesUsedNopublicFetchesUsed. Boolean.
intrusiveScanPerformedNointrusiveScanPerformed. Boolean.
singleWeakSignalMaliciousClaimedNosingleWeakSignalMaliciousClaimed. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that lookups reach external key-free public services, states the price ($0.04 USDC), and — most importantly — that an unpaid call returns x402 payment terms and does not execute. That payment-gate behavior is exactly the kind of operational detail annotations cannot express and prevents an agent from mistaking a 402 response for a failed analysis.

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 tight sentences, front-loaded with the core action and the interpretive caveat, then cost and transport details. The raw endpoint path adds little for an MCP caller, but nothing is padded or redundant.

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 exists, so return shape need not be explained, and the description covers cost, payment failure mode, and external-fetch behavior for a complex 21-param tool. The remaining gap is guidance on which of the many optional inputs actually drive a domain-history result.

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?

With 21 parameters and 100% schema description coverage, the schema already carries the burden. The description adds only a high-level framing ('caller fields and optional key-free public lookups') that hints at the enrichment toggles (publicDns, fetchRdap, fetchCrtSh, etc.) without explaining which to enable or what caller-supplied domains/feeds change. Baseline 3 is appropriate.

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: analyze publicly accessible domain history plus DNS/RDAP context. The scope (domain history and registration/DNS signals) is distinct enough from siblings like typosquatting-domain-detect or exposed-service-risk-analyze, though the description never names or contrasts an alternative.

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?

Implies usage via the caveat 'History attributes alone are not malice,' which tells the agent how to read results, and mentions optional key-free public lookups. It gives no explicit when-to-use or when-not-to-use condition and does not point at any sibling for related queries (e.g., IOC enrichment or phishing clustering).

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