Skip to main content
Glama

BRAINIAC Email & Communication Security

Detect phishing signals

email-security_phishing-signal-detect

Identify phishing indicators in caller-supplied email content and URLs (urgency phrases, lookalike hosts, IP URLs, password forms). Indicators are not confirmed malicious activity. Price $0.04 USDC. POST /api/v1/email-security/phishing-signal-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_phishing-signal-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.3/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does disclose non-obvious operational behavior: cost ($0.04 USDC), the transport (POST /api/v1/email-security/phishing-signal-detect), and the failure mode (unpaid calls return 402 and do not run). The 'not confirmed malicious activity' caveat is a genuinely useful interpretive constraint. It still omits whether URL/DNS lookups leave the caller's data (relevant given followPublicUrls/publicDns params) and says nothing about determinism or response shape.

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, front-loaded with the purpose and indicator list, then caveat, then commercial terms. Every sentence carries information; the endpoint path is mildly redundant but defensible for a paid POST API.

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 this complex — 19 optional parameters, deeply nested email/attachment/conversation objects, no output schema, no annotations — the description covers almost none of the decision-relevant surface. It never says how to choose an input mode, which fields are mutually exclusive, or what the response contains, leaving an agent unable to construct a correct call from the description alone.

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 with nested objects, so the schema itself explains nothing. The description only vaguely gestures at 'email content and URLs' and never clarifies the multiple input modes (text vs eml vs csv vs json vs file vs emails[] vs conversations[]), the role of followPublicUrls, publicDns, dkimSelectors, asOf, brandDomains or companyNames, or how supply of one mode interacts with another.

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?

Names a specific verb and resource ('Identify phishing indicators in caller-supplied email content and URLs') and enumerates the signal classes it looks for, so an agent knows exactly what it gets. It does not, however, differentiate itself from close siblings such as bec-pattern-detect, spoofing-detect or url-chain-analyze, so boundary selection still requires guessing.

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 by scoping inputs to 'caller-supplied email content and URLs' and by warning that 'Indicators are not confirmed malicious activity', which tells the agent to treat output as weak signal. There is no explicit when-to-use / when-not-to-use statement and no routing to any of the seven sibling tools that cover adjacent analyses.

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