Skip to main content
Glama

Domain Checks Bundle Payment Quote

domain_trust_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/domain/trust (base $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 (one .com, .net or .org name per call). Domain checks bundle for one .com, .net or .org domain in one call: registry facts (registrar, created/expiry, status), TLS certificate (issuer, days to expiry, hostname match), MX/SPF/DMARC, HTTP security headers (redirects not followed), with a 0-100 check score and its reasons. Other TLDs refused before payment. USDC on Base or Polygon. Buyer terms: results may not be used for marketing, spam or any unsolicited commercial message or solicitation, or to compile or resell a registration database. 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 suc

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_trust_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?

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses pricing ($0.25 base), accepted chains and tokens, refund/charge behavior on failure per rail, and legal use restrictions. That is substantial behavior an agent cannot get from the structured fields, though the final Polygon settlement clause is cut off mid-word, leaving one policy 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?

The description is a dense multi-clause run-on that repeats 'USDC on Base or Polygon' and the domain-scope rule, buries the payment mechanics mid-paragraph, and terminates abruptly ('is settled only when it suc'). The useful core (what the bundle returns, how to pay, what is refused) is not front-loaded cleanly.

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, it covers price, rails, refusal rules and buyer terms well. However, it never describes the shape of the quote returned (amounts, fields, expiry) and the text is truncated, so it falls short of fully equipping an agent to use the result.

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 input schema is empty (0 params), so baseline is 4. The description does add the real invocation semantics that the schema cannot express: the domain is supplied as an HTTP query parameter ('GET ?domain=example.com'), exactly one name per call, and only .com/.net/.org are accepted.

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?

It states a specific verb+resource ('Returns the payment terms for .../api/domain/trust') and immediately clarifies scope ('this tool never runs the check or pays'). It also enumerates what the paid bundle covers (registry facts, TLS, MX/SPF/DMARC, HTTP headers), which implicitly distinguishes it from domain_whois_quote and domain_ssl_quote, though it never names those siblings directly.

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?

It gives operational guidance (pay the 402 over HTTP with x402 v2, one .com/.net/.org per call, other TLDs refused before payment), which is real when-to-use context. But it never explicitly routes the agent between this bundle and the narrower siblings (domain_whois_quote, domain_ssl_quote, domain_precheck_quote), leaving the choice 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.