Skip to main content
Glama

BRAINIAC Email & Communication Security

Detect email spoofing indicators

email-security_spoofing-detect

Detect sender spoofing indicators from supplied SPF/DKIM/DMARC authentication results and optional public DNS TXT evidence. Not a confirmed spoof verdict without multi-signal evidence. Price $0.05 USDC. POST /api/v1/email-security/spoofing-detect. 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_spoofing-detect"
  }
}

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.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose genuinely useful operational facts: price ($0.05 USDC), endpoint (POST /api/v1/email-security/spoofing-detect), and that unpaid calls return 402 without executing. It also flags the epistemic limit of the result (indicators, not a confirmed verdict), but says nothing about required input combinations, rate limits, or latency.

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, then the confidence caveat, then the commercial/transport facts. No redundant restatement of the title, though the endpoint path largely duplicates the tool name's information.

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 19-parameter tool with deeply nested objects, zero schema descriptions, no annotations, and no output schema, the description is well short of what an agent needs to assemble a valid call or know what comes back. The payment/dispatch facts are covered, but input meshing and result shape are not.

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 nested, so the description must compensate and largely fails to. It illuminates only the authentication-results and public-DNS/DKIM-selector inputs; the bulk of the surface (eml, csv, files, emails, conversations, brandDomains, companyNames, urls, urlHops, followPublicUrls, asOf) is left unexplained.

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 ("Detect sender spoofing indicators") and names the evidence it consumes: SPF/DKIM/DMARC authentication results plus optional public DNS TXT evidence. That scoping usefully separates it from broader siblings like phishing-signal-detect or header-forensics, though no sibling is named explicitly.

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 rather than stated: the tool is for cases where authentication results and/or DNS TXT evidence are available, and "Not a confirmed spoof verdict without multi-signal evidence" sets an interpretive boundary. There is no explicit when-to-use-vs-alternative guidance against domain-impersonation-check or header-forensics.

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