Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_api_email_mx_forensics

Inspect an email address's MX records and provider details to identify its mail infrastructure and routing.

Instructions

[Web Intelligence] MX / provider forensics for an email address Measured p50 12 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://api.caelaralabs.com.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "email": "<email>"
    },
    "name": "caelara_api_email_mx_forensics"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesEmail address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/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 supply genuinely useful behavioral facts: an external network call to api.caelaralabs.com and measured p50/p95 latency with a benchmark date. It omits whether the operation is read-only, whether results are cached or rate-limited, and what the response contains — real gaps for a tool with zero annotation coverage.

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?

Two short sentences with the purpose front-loaded and no filler. The benchmark and endpoint notes are marginal but compact; the missing punctuation between the purpose clause and the latency sentence slightly hurts readability.

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?

With no output schema and no annotations, the description needed to explain what comes back (MX hosts, provider name, confidence, diagnostics), and it does not. For a "forensics" tool with an undefined return shape, an agent cannot anticipate or interpret results from this definition alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single "email" parameter, so the baseline of 3 applies. The description adds no meaning beyond the schema — notably it does not clarify whether only the domain portion is used or whether the local part affects results.

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?

"MX / provider forensics for an email address" names a specific operation and resource: resolving mail-exchange/provider information from an email address. It is clear enough to distinguish from the disposable-email DB or SPF/DMARC grader siblings, though it never explicitly contrasts itself with them.

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 only weakly implied by the phrase "forensics" — an agent can infer this is for mail-infrastructure investigation. There is no statement of when to prefer this over caelara_compliance_disposable_email_db or caelara_compliance_spf_dmarc_grader, and no prerequisites or exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools