Skip to main content
Glama

PingValid Email Validation

by com.pingvalid
OverviewDiscussionsAdmin

Submit bulk validation job

pingvalid_submit_bulk_job

Submit up to 1000 email addresses for asynchronous validation. Returns immediately with a job_id; poll pingvalid_get_job_status until it completes. Requires the validate:bulk scope.

Input Schema

NameRequiredDescriptionDefault
tierNoPricing depth: quick (T1–T5) | standard (T1–T6, default) | deep (T1–T7, needs a paid plan or a top-up).standard
emailsYesUp to 1000 email addresses to validate in one batch.
legitimate_interestYesMust be true. Asserts the submitter has a legitimate interest in validating these addresses (required by the Terms of Service).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / tier / description
      Added value: +"Pricing depth: quick (T1–T5) | standard (T1–T6, default) | deep (T1–T7, needs a paid plan or a top-up)."
    • removedInput schema / properties / webhook_url
      Removed value: -{
-  "description": "Optional HTTPS URL — receives an HMAC-signed completion event.",
-  "format": "uri",
-  "type": "string"
-}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Adds real context beyond the annotations: asynchronous execution, immediate return with a job_id, and a required validate:bulk scope (auth requirement). Annotations already cover the read-only/idempotency/destructive profile, so the remaining gap is minor.

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?

Three short sentences, front-loaded with the action and capacity, then the async follow-up, then the prerequisite. No filler.

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?

No output schema exists, yet the description still explains the return value (job_id) and the polling workflow, and it discloses the required scope. An agent has everything needed to invoke and follow up correctly.

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 description coverage is 100%, including the tier enum's pricing-depth semantics and the legitimate_interest constraint, so the schema carries the parameter burden. The description only restates the 1000-address cap and adds no new parameter meaning; baseline 3 applies.

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 ('Submit ... email addresses for asynchronous validation') plus a concrete capacity bound ('up to 1000'). This clearly separates it from the single-address sibling pingvalid_validate_email and from the polling siblings.

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?

Explicitly tells the agent what happens next: 'Returns immediately with a job_id; poll pingvalid_get_job_status until it completes,' naming the follow-up sibling. It does not explicitly contrast bulk vs. single validation, but the async/batch framing makes the choice inferable.

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

All PingValid Email Validation 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