Skip to main content
Glama

Domain Pre-purchase Check Payment Quote

domain_precheck_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/domain/precheck (single $0.02, bulk $0.25; USDC on Base or Polygon); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET ?domain=example.com (tier=single), or POST {domains:[...]} with tier=bulk. Registration verdict (registered, likely_unregistered or unknown) with age and status flags from registry RDAP, DNS, TLS, a look-alike similarity signal and an optional OFAC SDN address screen. Failed or throttled sources are unknown, never available. Not a guarantee of availability or safety; not legal advice. .dev and .app are not supported: a request with only those names is refused before payment; in a bulk batch they are removed before payment and the flat price still applies. 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

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": "domain_precheck_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Well beyond the annotations, it discloses pricing ($0.02 single / $0.25 bulk), accepted chains and tokens, x402 v2 payment mechanics, TLD refusal behavior, and crucially the per-chain charging-on-failure differences (Base vs Solana vs XRP Ledger vs Polygon). That is exactly the kind of context readOnlyHint and idempotentHint cannot carry; the score is held at 4 because the final polygon sentence is cut off mid-clause, leaving a settlement rule incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense paragraph packing pricing, protocol, verdict fields, disclaimers and four chain-specific charging rules, with nested parentheticals and a dangling truncated final sentence. The lead is front-loaded and does its job, but much of the middle (OFAC screen, look-alike signal, 'not legal advice') describes the downstream report, not the quote being returned here.

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?

With no parameters and no output schema, the description must explain what the quote actually contains, and it only partly does – it names price and tiers but never describes the response shape (payment requirements, quote identifiers, expiry). The truncation leaves the Polygon settlement rule unfinished, so an agent is left with an unresolved behavioral question.

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?

Zero parameters, so the baseline is 4. The description goes further by documenting the two request shapes (GET ?domain= with tier=single, POST {domains:[...]} with tier=bulk) even though neither appears in the empty schema, which is genuinely additive.

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?

The first clause is specific: it 'Returns the payment terms' for a named URL and explicitly says it 'never runs the check or pays', which separates the quote from the paid endpoint. It never names the adjacent domain_ssl_quote / domain_whois_quote / domain_trust_quote siblings, so an agent must infer the split; and a large share of the text describes the underlying check's verdict rather than this tool's own output, which blurs what actually comes back.

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?

Usage is only implied: you call it to learn the price, then pay over HTTP with x402 v2. There is useful exclusion detail (.dev/.app refused before payment; in bulk they are stripped and the flat price still applies), but no explicit statement of when to pick this over the sibling domain lookup tools, which is the main routing decision an agent faces here.

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.