Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_compliance_disposable_email_db

Detect disposable or throwaway email domains and role accounts to support compliance and trust checks; submit an email address or domain for validation.

Instructions

[Compliance & Trust] Detect disposable / throwaway email domains and role accounts Measured p50 12 ms, p95 16 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://compliance.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_compliance_disposable_email_db"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesEmail address or domain

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses only latency figures and the upstream endpoint. It never says what the result is (boolean, score, category list), whether role accounts and disposable domains are distinguished in output, or whether the call is a pure read lookup; for a tool with zero annotation coverage this is a substantial gap.

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?

It is short and front-loaded: purpose first, then benchmark and endpoint. The latency telemetry and raw URL are arguably filler for an agent deciding how to call the tool, but they do not obscure the core statement.

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?

With one simple parameter and no output schema, the definition is complete enough to invoke but not to interpret. The biggest missing piece is what the call returns and how an agent should act on a positive disposable-domain or role-account match.

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% and the single parameter is already documented as 'Email address or domain'. The description hints that both input forms (domain and role-account address) are handled, but adds no clarification on normalization behavior or whether a bare domain versus full address changes the result.

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 ('Detect') and two concrete targets: disposable/throwaway email domains and role accounts. That is far more precise than the tool name alone, but it never distinguishes this lookup from sibling compliance tools such as caelara_compliance_domain_trust_composite.

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?

There is no explicit when-to-use guidance, no prerequisites and no exclusions. At best the '[Compliance & Trust]' tag implies a compliance/lead-hygiene context, and the agent is left to guess whether this is a pre-check before domain_trust_composite or an alternative to it.

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