Skip to main content
Glama

Audit signup email domains

check_domains
Read-onlyIdempotent

Checks up to 50 email domains (for example the domains of recent signups) and says which are disposable, which cannot receive mail, and which look fine. Send only domains, never full addresses.

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": {
      "domains": "<domains>"
    },
    "name": "check_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesEmail domains such as mailinator.com or gmail.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's job is to add the rest. It does: batch ceiling of 50, the three verdict classes returned, and the hard constraint that only bare domains are accepted. It does not say what happens to malformed or mixed input, but the essential behavioral context is present.

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?

Two sentences, no filler. The capability and its output classes come first, and the input constraint lands as a closing imperative where it is most likely to be acted on.

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

Completeness4/5

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

For a one-parameter read-only tool with annotations and no output schema, this covers nearly everything an agent needs: what it accepts, how much, and the categories of answer. Only the exact response shape per domain and error handling are unstated, which are minor for a tool this simple.

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?

Schema coverage is 100% for the single parameter, so the baseline is 3. The description earns above baseline by clarifying that entries must be bare domains and never full addresses, a distinction the schema's example ('mailinator.com') only implies.

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

Purpose5/5

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

The description gives a specific verb (checks), a specific resource (email domains), a bounded scope (up to 50), and enumerates the output categories (disposable, cannot receive mail, fine). An agent can distinguish this from check_email purely on the 'domains, never full addresses' framing without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It supplies a concrete use context ('for example the domains of recent signups') and an input constraint that implicitly routes full addresses to a sibling. It stops short of explicitly naming check_email or how_to_block as the alternative for non-domain work, so the exclusion is inferred rather than stated.

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