Skip to main content
Glama

Show an email check and its results

get_email_check
Read-only

Show one email check: status (checking, completed, expired, pending_approval, cancelled), counts, credited_cents, credits (each store credit with its kind and why) and, once completed, every address as {email, result, reason, suggestion?}. While checking: results_so_far (the sure answers so far, which never change), answered and pending. Poll it after check_emails; list_email_checks finds older ones. Results are deleted 7 days after the check completes (expired: counts only). results false leaves out the results and results_so_far. Unknown id: 404 check_not_found.

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": {
      "check_id": "ec_exampleexampleexample2"
    },
    "name": "get_email_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
resultsNofalse: leave the results out (default true).
check_idYesCheck id (ec_...) from check_emails or list_email_checks.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "check_id": "ec_exampleexampleexample2"
      +  }
      +]
    • 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.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds substantial context beyond them: results are deleted 7 days after completion, expired checks return counts only, unknown ids return 404 check_not_found, and results=false suppresses both results and results_so_far. It also explains state-dependent response shape (during checking: results_so_far, answered, pending).

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?

Heavily front-loaded with the return shape first, then lifecycle/deletion rules, then the results flag, then the error case — a logical order with no filler sentences. The telegraphic, parenthetical style packs a lot into few words, which is efficient but slightly dense to parse on a first read.

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 carries the full burden of describing return values and it does so field-by-field, including state-dependent variants and the error case. Nothing an agent needs to call this correctly or interpret the response appears to be missing.

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 would be 3, but the description adds real meaning for the results flag by naming the two fields it suppresses (results and results_so_far), which the schema does not specify. check_id and passport_token semantics are left to the schema, which already documents them adequately.

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?

Opens with a specific verb+resource ("Show one email check") and then enumerates exactly what is returned: status with its five enumerated values, counts, credited_cents, credits with kind and why, and per-address {email, result, reason, suggestion?}. It also distinguishes itself from siblings by saying list_email_checks finds older checks and that it should be polled after check_emails.

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?

Explicit routing is given: after running check_emails, poll this tool; for older checks, use list_email_checks. That covers both the when-to-use condition and the alternative to pick instead, so an agent can choose correctly without opening another schema.

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.