Skip to main content
Glama

BRAINIAC Email & Communication Security

Analyze email URL redirect chains

email-security_url-chain-analyze

Analyze caller-supplied redirect hops or optionally follow public URLs with strict SSRF protections. Never sends email content to external scanners. Price $0.05 USDC. POST /api/v1/email-security/url-chain-analyze. 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_url-chain-analyze"
  }
}

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 add real behavior: outbound fetching of public URLs under strict SSRF protections, no email content sent to external scanners, a $0.05 USDC price, and 402 semantics for unpaid calls. It still omits what the analysis returns, pagination/size limits, and how the many input modes interact, which matters for a nested 19-parameter tool.

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 core action and the two processing modes, with no filler. The endpoint path and price lines are borderline but the payment/402 detail is operationally necessary given no annotations.

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?

The tool has 19 parameters, deeply nested objects, no output schema, and no annotations, yet the description explains almost none of the input surface or the returned result. For this complexity level it leaves too much for the agent to infer.

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. It only implicitly touches urlHops and followPublicUrls, leaving eml, csv, json, text, urls, emails, conversations, files, attachments, publicDns, brandDomains, and dkimSelectors completely unexplained in both schema and description.

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?

The description uses a specific verb+resource: analyze caller-supplied redirect hops, optionally following public URLs. That tells an agent what the tool does without opening the schema. It does not explicitly distinguish itself from siblings like header-forensics or phishing-signal-detect, so it stops short of a 5.

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?

It distinguishes two modes — analyzing hops the caller already has vs. actively following public URLs — which is useful selection guidance. However, it gives no guidance on when to choose this tool over the sibling email-security tools, and no conditions for the 19 input modes.

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