Skip to main content
Glama

AgentMart

by ai.ciphyr.agentmart
OverviewDiscussionsAdmin

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; nothing is ever sent to the addresses. 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.

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.6/5.0
Behavior5/5

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

Despite annotations already covering safety hints, the description adds substantial behavioral context: pricing and credit structure, consent requirement, asynchronous processing, owner approval for larger orders, concurrency and daily limits, and the fact that no email is ever sent. These are exactly the operational details an agent needs beyond the annotation flags.

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?

The description is front-loaded with the core purpose and remains focused on operational constraints, pricing, consent, and follow-up behavior. It is dense and lengthy in a single paragraph, and could be organized more clearly, but most sentences earn their place given the tool's complexity.

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 compensates by explaining the returned statuses and reasons, the polling flow via get_email_check, pricing, consent, limits, and approval behavior. An agent has enough context to invoke the tool correctly and understand what happens afterward.

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 description coverage is 100%, so the baseline is 3. The description adds useful semantics beyond the schema by explaining that pricing is counted by different entries, that some lists may cost only $1, and by emphasizing that consent must be truthfully asserted; it does not explain every parameter such as label or inbox_instance_id, so it is not a full 5.

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 states a specific verb and resource: checking the owner's own email addresses, up to 1000 at a time, returning valid/invalid/risky/unknown outcomes. It also distinguishes this operation from the follow-up status tool by saying to call get_email_check until completed.

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 clearly says when to use the tool (before sending to an owner-owned opt-in list) and gives the required follow-up action, as well as explicit exclusions about never supplying or sending to addresses. However, it does not name competing sibling tools such as check_sender or suppression_check, so alternative selection is largely implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AgentMart toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources