Skip to main content
Glama

OpenBait Lookalike Domains

Check lookalike domains

check_lookalike_domains
Read-onlyIdempotent

Find registered lookalike domains of a brand's website: the brand's name on other endings, with common words such as login or pay, as .shop names of the kind copied stores use (also for the shorter name a brand goes by when its domain ends in a word such as supply or store), and a few misspellings. Checks which of them resolve in DNS and what their front page shows (a page using the brand's name, another live site, or nothing); a misspelling counts only when its page uses the brand's name, and a name that lands on the brand's own site is left out. Returns how many were found and at most five of them. Read-only. Same check as https://openbait.com/tools/typosquat-check.

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

Input Schema

NameRequiredDescriptionDefault
domainYesthe brand's website, e.g. example.com or https://www.example.com

Output Schema

NameRequiredDescriptionDefault
domainYesthe registrable domain that was checked
summaryYes
resultUrlYesthe same result on openbait.com
lookalikesYesat most five registered lookalikes, names using the brand's name first

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • addedOutput schema / properties / lookalikes / description
      Added value: +"at most five registered lookalikes, names using the brand's name first"
    • removedOutput schema / properties / lookalikes / items / properties / activeDns
      Removed value: -{
      -  "description": "the name resolves in DNS",
      -  "type": "boolean"
      -}
    • addedOutput schema / properties / lookalikes / items / properties / blocked
      Added value: +{
      +  "description": "live_other only: the site answered with a bot check, so its page was not read",
      +  "type": "boolean"
      +}
    • removedOutput schema / properties / lookalikes / items / properties / mutationType
      Removed value: -{
      -  "description": "homoglyph, keyword, omission, transposition or tld_swap",
      -  "type": "string"
      -}
    • removedOutput schema / properties / lookalikes / items / properties / score
      Removed value: -{
      -  "description": "0-100, higher is more likely to be mistaken for the brand",
      -  "type": "integer"
      -}
    • removedOutput schema / properties / lookalikes / items / properties / severity
      Removed value: -{
      -  "description": "high or medium",
      -  "type": "string"
      -}
    • changedOutput schema / properties / lookalikes / items / properties / site / description
      Previous value: -"for names that resolve: brand_page (page uses the brand's name), redirects_to_you (ends on the brand's own domain), live_other or no_site"New value: +"what the front page shows: brand_page (uses the brand's name), live_other (another live site), no_site (nothing there) or unread (registered, page not read in time)"
    • changedOutput schema / properties / lookalikes / items / required
      Previous value: -[
      -  "domain",
      -  "severity",
      -  "score",
      -  "mutationType",
      -  "activeDns"
      -]New value: +[
      +  "domain",
      +  "site"
      +]
    • removedOutput schema / properties / summary / properties / activeDns
      Removed value: -{
      -  "type": "integer"
      -}
    • addedOutput schema / properties / summary / properties / checked
      Added value: +{
      +  "description": "how many names were looked up in DNS",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / summary / properties / found
      Added value: +{
      +  "description": "how many registered lookalikes were found",
      +  "type": "integer"
      +}
    • addedOutput schema / properties / summary / properties / more
      Added value: +{
      +  "description": "how many of found are not listed in lookalikes",
      +  "type": "integer"
      +}
    • removedOutput schema / properties / summary / properties / reviewNow
      Removed value: -{
      -  "type": "integer"
      -}
    • removedOutput schema / properties / summary / properties / totalCandidates
      Removed value: -{
      -  "type": "integer"
      -}
    • removedOutput schema / properties / summary / properties / watchlist
      Removed value: -{
      -  "type": "integer"
      -}
    • changedOutput schema / properties / summary / required
      Previous value: -[
      -  "totalCandidates",
      -  "reviewNow",
      -  "activeDns",
      -  "watchlist"
      -]New value: +[
      +  "checked",
      +  "found",
      +  "more"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Goes well beyond the supplied readOnlyHint/openWorldHint/idempotentHint annotations by disclosing the filtering logic (misspellings only count when the page uses the brand name; names resolving to the brand's own site are excluded) and the output cap of five results. It does not mention runtime, rate limits, or how long a scan takes, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded correctly, but the body is one long compound sentence with nested parentheticals that is hard to parse on first read. No sentence is wasted, yet the structure works against quick scanning.

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

Completeness5/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 not be explained, yet the description still states the count plus the five-result cap. For a read-only, single-parameter tool this covers everything an agent needs to call it and interpret the result.

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?

With a single parameter at 100% schema coverage the baseline is 3, but the description adds real meaning about how the input is used: the domain is treated as the brand's website, and the shortened-name behavior ('when its domain ends in a word such as supply or store') explains derivation from the input string. That clarification is not present in the schema.

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?

States a specific verb and resource ('Find registered lookalike domains of a brand's website') and then enumerates the exact categories it generates: other endings, common words like login/pay, .shop copies, shortened brand names, and misspellings. An agent knows exactly what the tool produces before opening any schema.

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 through 'Read-only' and a reference link to the equivalent web tool, which suggests a safe investigative check, but gives no explicit when-to-use or when-not-to-use guidance and names no alternatives (none exist as siblings). The scope is inferable but not directed.

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