Skip to main content
Glama

BRAINIAC Email & Communication Security

Check domain impersonation

email-security_domain-impersonation-check

Identify domains resembling supplied company or brand domains using edit distance, hyphen variants, homoglyph folding, and brand-token embedding. Resemblance is not proof of abuse. Price $0.03 USDC. POST /api/v1/email-security/domain-impersonation-check. Unpaid calls return 402 and do 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": "email-security_domain-impersonation-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
emlNo
asOfNo
fileNo
jsonNo
textNo
urlsNo
filesNo
emailsNo
headersNo
urlHopsNo
publicDnsNo
attachmentsNo
brandDomainsNo
companyNamesNo
conversationsNo
dkimSelectorsNo
followPublicUrlsNo
authenticationResultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and handles the important operational traits well: exact price ($0.03 USDC), HTTP method and path, and the failure mode where unpaid calls return 402 and do not execute. It stops short of describing response shape, scoring thresholds, or whether results are ranked, which keeps it out of the top band.

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 with the core purpose front-loaded, followed by the interpretation caveat, cost, endpoint, and payment failure behavior. Nothing is padded, though the endpoint path duplicates the tool name somewhat.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 19 mostly nested parameters, zero schema descriptions, and no output schema, the definition is far too thin — an agent cannot know which of the many input modes to populate or what the result will look like. The payment and endpoint details are useful, but the input-contract gap is significant.

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% across 19 parameters, many of them deeply nested (emails, conversations, attachments, urlHops, authenticationResults), so the description must compensate and largely does not. The only hint is 'supplied company or brand domains', which loosely points at brandDomains/companyNames but leaves the primary content inputs (csv, eml, text, json, file, emails) and options like asOf, publicDns, dkimSelectors, and followPublicUrls entirely unexplained.

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 ('Identify') and resource ('domains resembling supplied company or brand domains') and names the detection techniques used (edit distance, hyphen variants, homoglyph folding, brand-token embedding). This is concrete enough that an agent can tell it apart from a spoofing or BEC pattern tool just from the text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description never says when to reach for this tool versus the sibling spoofing-detect, bec-pattern-detect, or phishing-signal-detect tools, and gives no prerequisites beyond the fact that brand/company domains must be supplied. The line 'Resemblance is not proof of abuse' is interpretation caution, not usage routing.

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