Skip to main content
Glama

BRAINIAC Threat Intelligence & Public Signals

Detect typosquat domains

threat-intelligence_typosquatting-domain-detect
Read-onlyIdempotent

Identify domains resembling supplied brand or company domains using local string/keyboard heuristics. Resemblance alone is not confirmed phishing. Price $0.03 USDC. POST /api/v1/threat-intelligence/typosquatting-domain-detect. 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_typosquatting-domain-detect"
  }
}

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.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive) and open-world scope, but the description adds genuinely non-obvious behavior: a $0.03 USDC price, an x402 payment gate, and the fact that an unpaid call returns payment terms without executing. The false-positive caveat further characterizes output reliability.

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?

Five short sentences, front-loaded with purpose and method, then the caveat, then pricing and transport details. Each sentence carries information, though the raw endpoint path is marginal value for an agent.

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?

An output schema exists, so return values need no explanation, and the payment gate is well covered. However, with 21 optional parameters and zero required ones, the description should state the minimum viable input (e.g. brands or candidates) and never does.

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 description coverage is 100%, so every one of the 21 parameters is already documented in structured data; the description adds no parameter-level meaning. Baseline 3 applies, and notably it never tells the agent which of brands/candidates/domains to populate.

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 verb and resource ('Identify domains resembling supplied brand or company domains') and names the mechanism ('local string/keyboard heuristics'), which separates it from sibling clustering or history tools. It does not explicitly name an alternative sibling, so it stops 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: you supply brand/company domains and get lookalike candidates back. The line 'Resemblance alone is not confirmed phishing' is interpretation guidance, not routing guidance, and there are no when-not-to-use conditions or named alternatives.

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