Skip to main content
Glama

Check a list of my owner's email addresses

check_emails
Destructive

Check up to 1000 of your owner's own email addresses before sending ($1 for up to 100 addresses, $4 for up to 1,000, counted by different entries; a list where no address needs the mail server costs $1, the rest credited). Each comes back valid, invalid, risky or unknown with a reason. For the sending domain's DNS, use check_sender. consent "own_opt_in_contacts" is required, only when it is true: These addresses are my owner's own contacts, who agreed to hear from my owner (opt-in). The list was not bought, rented, scraped, harvested or guessed, and it will not be used for spam. We check a list your owner already has. We never supply, find, guess, enrich or sell addresses, and we never send anything to them. Then call get_email_check about once a minute until completed. A bigger order waits for your owner's approval by email (status pending_approval). Limits: 2 lists open at once per owner and 10 lists per 24 hours. Retries, refusals and credits: /llms/email-check.md.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "emails": [
        "one@example.com"
      ],
      "consent": "own_opt_in_contacts",
      "idempotency_key": "example-list-1",
      "max_price_cents": 100
    },
    "name": "check_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoYour own short name for the list (a plain name, up to 60 characters), shown to your owner in the approval email.
emailsYesYour owner's own contacts, plain addresses.
consentNoRequired: "own_opt_in_contacts", your statement, only when it is true.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.
idempotency_keyNoReuse with the same list to retry safely without paying twice.
max_price_centsNoThe most this may cost, in US cents.
inbox_instance_idNoOne of your owner's webhook inboxes: the completion event (counts only) is written there.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "consent": "own_opt_in_contacts",
      +    "emails": [
      +      "one@example.com"
      +    ],
      +    "idempotency_key": "example-list-1",
      +    "max_price_cents": 100
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare mutating, destructive, non-idempotent and open-world behavior but say nothing about cost or process; the description fills that with concrete pricing tiers and credit rules, the four result categories with reasons, the asynchronous polling requirement, the owner-approval gate, and hard limits (2 open lists, 10 per 24h). Nothing here repeats what the annotations already encode.

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?

The operational content is front-loaded and useful, but the middle is padded with legal boilerplate ('not bought, rented, scraped, harvested or guessed... never supply, find, guess, enrich or sell') plus a docs URL, and pricing is crammed into a parenthetical that is hard to parse. It earns partial credit for ordering, not for length.

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

Completeness5/5

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

With no output schema, the description still tells the agent what comes back (valid/invalid/risky/unknown plus a reason), how to retrieve it, what blocks completion, and what the cost ceiling means. Nothing material is left for the agent to discover by trial.

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%, so the baseline is 3. The description adds real meaning beyond the field docs: it ties list size to pricing tiers (100 vs 1,000), reinforces that consent may only be supplied when literally true, and explains the approval consequence of larger orders, which is context an agent needs when choosing max_price_cents and label.

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?

States a specific verb and resource ('Check up to 1000 of your owner's own email addresses before sending') and explicitly draws the boundary against the sibling check_sender ('For the sending domain's DNS, use check_sender'). An agent can distinguish this from every other check_* tool without opening a schema.

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

Usage Guidelines5/5

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

Names the alternative (check_sender) and the condition that selects it, states the prerequisite consent assertion, and gives the follow-up protocol ('call get_email_check about once a minute until completed') plus the large-order approval path (pending_approval). When-to-use, when-not-to-use and next step are all present.

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.