Skip to main content
Glama

Caelara Labs Web Intelligence

email_mx_forensics

MX / provider forensics for an email address

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": "email_mx_forensics"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesEmail address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must carry the full behavioral burden, and it does not. It does not disclose whether this performs a live DNS lookup (network latency, rate limits, possible timeouts), whether it is read-only, or what the response contains.

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

Conciseness3/5

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

It is a single short noun phrase with no filler, so nothing is wasted, but the terseness comes at the cost of under-specification. Brevity here reflects missing content rather than disciplined editing.

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 single-param, annotation-free tool with no output schema, the description should at minimum indicate what is returned (MX hosts, provider name, risk flags). None of that is present, so an agent cannot predict the result shape or cost of the call.

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

Parameters4/5

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

There is a single parameter, `email`, with a schema description of "Email address" and 100% coverage. The description adds nothing beyond the schema, but for a one-parameter tool the schema alone is sufficient, so the baseline of 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"MX / provider forensics for an email address" identifies the resource (MX records / mail provider) and the input domain, but "forensics" is vague about the actual operation — it never states whether it looks up live MX/DNS records, infers a provider, or assesses deliverability risk. An agent can guess it is DNS/provider-related but not what it produces.

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 when-to-use guidance at all. There is no mention of when MX forensics is preferable to a verification tool such as lead_verify_composite, and no preconditions 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources