Skip to main content
Glama

Email Address Check Payment Quote

email_check_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/email/check (base $0.003; USDC on Base or Polygon); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET ?email=name@example.com (one address per call). Email address check for one address: RFC 5322 syntax, MX records (null MX noted), SPF and DMARC records over DNS, role-account flag (info@, admin@ and similar) and a disposable-domain match. No SMTP connection is made, so mailbox existence is not checked. One address per call. Bad input or DNS failure: Not charged. USDC on Base or Polygon. On USDC on Base, errors are not charged, apart from the exceptions noted on a route. On USDC on Solana, and RLUSD on the XRP Ledger, a refused or failed request may still be charged. On Polygon (native USDC), a request is settled only when it succeeds (HTTP status below 400). Failed requests are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "email_check_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered structurally. The description does add genuinely useful context beyond that (no SMTP, mailbox existence not checked, per-chain charging and settlement rules, errors uncharged on Base/Polygon vs possibly charged on Solana/XRP), but it also repeats chain/currency facts three times rather than consolidating them. This is helpful but only partly disciplined.

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 payment/settlement facts are front-loaded and relevant, but the text bloats unnecessarily: 'base $0.003; USDC on Base or Polygon' and related currency statements recur multiple times, 'One address per call' appears twice, and the charging rules are scattered across sentences rather than grouped. Much earns its place; the duplication does not.

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

Completeness3/5

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

For a zero-parameter quote tool with no output schema and strong annotations, the description covers inputs, price, and settlement behavior well. It remains ambiguous about what the returned quote actually contains (the 402 payment requirements structure) and how the agent should then proceed to actually run the check, which is the natural next step for a quote tool.

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?

The tool has zero parameters, so baseline is 4. The description still adds meaning by showing the input is conveyed as a query string (?email=name@example.com, one address per call) and defines what the underlying check covers, which is more than the empty schema conveys.

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

Purpose4/5

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

States a specific verb and resource: 'Returns the payment terms for https://horizonpulse.dev/api/email/check', and immediately clarifies 'this tool never runs the check or pays', which distinguishes a quote tool from a check-execution tool. It never names the specific sibling quote tools (e.g., domain_precheck_quote) it must be differentiated from, so it stops short of a 5.

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

Usage Guidelines3/5

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

Implies usage ('Pay the 402 over HTTP with x402 v2') and gives the endpoint shape, so an agent can infer this tool is used to price a check before paying. However, there is no explicit when-to-use vs when-not statement referencing alternatives, and the boundary with the many other *_quote siblings is left to inference.

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.