Skip to main content
Glama

Caelara Labs Compliance & Trust

disposable_email_db

Detect disposable / throwaway email domains and role accounts

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

Input Schema

NameRequiredDescriptionDefault
emailYesEmail address or domain

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, yet it says nothing about what 'detect' returns (boolean, score, category), whether role-account detection requires a full address versus a bare domain, or how the two checks are combined. It also doesn't note inference limits or that a domain-only input cannot yield role-account results.

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?

One short, front-loaded sentence with no filler or repetition. Brevity is appropriate for a one-parameter lookup, though the terseness is what leaves the behavioral and usage gaps unaddressed.

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 simple single-parameter lookup with no output schema, the definition covers the core purpose but leaves the agent guessing at the return shape and at how domain-only input is handled. It is minimally sufficient rather than complete.

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 'email' parameter is already documented as 'Email address or domain', so the schema does the heavy lifting. The description adds the concept of role accounts, which hints the local part matters, but it never resolves the tension with the schema accepting a bare domain.

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?

States a specific verb ('Detect') and a specific set of resources ('disposable / throwaway email domains and role accounts'), which is enough to distinguish it from the sibling checks like domain_trust_composite or sanctions_fuzzy_screen. It stops short of naming a sibling, so it lands at 4 rather than 5.

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 or when-not-to-use guidance, no mention of the signup/validation context it typically serves, and no pointer to alternatives such as the reputation or trust tools that overlap with domain checks. The use case is only faintly implied by the verb 'Detect'.

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