Skip to main content
Glama

BRAINIAC Email & Communication Security

Analyze email headers

email-security_header-forensics

Analyze caller-supplied email headers for routing hops and suspicious inconsistencies (From/Return-Path/Reply-To, auth results, dates). Indicators only—not confirmed malice. Price $0.04 USDC. POST /api/v1/email-security/header-forensics. 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_header-forensics"
  }
}

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

C2.9/5.0
Behavior3/5

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

With no annotations, the description does carry useful behavioral context: output is heuristic ('indicators only—not confirmed malice'), the call costs $0.04 USDC, and unpaid calls return 402 without executing. It omits whether external network lookups occur (the schema's publicDns/followPublicUrls parameters imply they may), rate limits, and any data-retention behavior.

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?

Three short sentences, front-loaded with the purpose and the interpretive caveat before the pricing/transport metadata. Little waste, though the endpoint and price sentence is operational detail rather than tool semantics.

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, deeply nested tool with no annotations and no output schema, this is thin. An agent cannot tell which of the many mutually overlapping input shapes to supply, nor what the response will contain, 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, so the description must compensate and largely does not. It names only header-level concepts (From, Return-Path, Reply-To, auth results, dates) and leaves the actual inputs—eml, headers, csv, urls, attachments, conversations, dkimSelectors, brandDomains, asOf—unexplained and unranked.

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?

A specific verb (analyze) plus resource (caller-supplied email headers) and the concrete artifacts it inspects: routing hops, From/Return-Path/Reply-To mismatches, auth results, dates. It implicitly separates itself from siblings that handle attachments or URL chains, though it never names them.

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?

No explicit when-to-use or when-not guidance and no named alternatives among the seven sibling email-security tools. The phrase 'caller-supplied email headers' is the only hint about the appropriate input mode, and it actually understates the tool's much broader accepted input set.

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