Skip to main content
Glama

BRAINIAC Email & Communication Security

Detect conversation tampering

email-security_conversation-tamper-detect

Identify inconsistencies between supplied email conversation copies (missing messages, body hash mismatches, header field divergence). Export artifacts are distinguished from confirmed tampering. Price $0.05 USDC. POST /api/v1/email-security/conversation-tamper-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_conversation-tamper-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

A3.5/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does disclose non-obvious behavior: a $0.05 USDC price, the POST endpoint path, and that unpaid calls return 402 without executing. It also flags an interpretive caveat that export artifacts are distinguished from confirmed tampering, which prevents over-reading results. It omits retention/statelessness and rate-limit behavior, keeping it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with what is detected, then the interpretive caveat, then the transactional and transport facts. No sentence is redundant and no important detail is buried.

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

Completeness3/5

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

For a high-complexity analyzer with no output schema, no annotations, and 19 undocumented parameters, the description covers the detection semantics and one output caveat but says nothing about the shape of the findings returned or how the many input formats (raw eml/csv/text vs. structured conversations) relate. Adequate to justify calling it, not adequate to call it confidently.

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, including nested email, attachment, conversation, and authenticationResults objects, so the description must compensate and largely does not. The only hint is 'supplied email conversation copies,' which loosely points at the conversations array; the roles of csv, eml, file, json, text, urls, asOf, dkimSelectors, publicDns, and brandDomains are left entirely 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?

The description names a specific verb (Identify) and resource (inconsistencies between supplied email conversation copies) and enumerates the three signals checked: missing messages, body hash mismatches, header field divergence. It does not differentiate from siblings like email-security_header-forensics, which overlaps on header analysis, so an agent gets a clear purpose but no sibling routing.

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?

The phrase 'between supplied email conversation copies' implies the caller must supply multiple copies of the same conversation to compare, which is real usage context. However, it never states when to prefer this over header-forensics or spoofing-detect, nor any prerequisite for having multiple copies.

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