Skip to main content
Glama

zato: Ethereum & Base Data API (pay-per-call x402)

Domain DNS & SSL certificate check

domain_check
Read-only

Check DNS records and SSL certificate of a domain (expiry, issuer, trusted). DNS records (A, AAAA, CNAME, MX, NS, TXT, CAA) and the live TLS certificate of a public domain: issuer, validity, days left, SANs, protocol and whether it is trusted. Price: $0.001 USDC per call (x402 v2, Base). Free demo: https://api.zato.org/demo/domain/check

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "domain_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name, e.g. example.com (no scheme, no path)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations cover read-only and open-world safety, and the description adds genuinely non-structured context: a per-call cost of $0.001 USDC via x402 v2 on Base, plus a free demo URL for testing before paying. It also constrains scope to public domains and previews the return payload since no output schema exists. It stops short of stating failure behavior (NXDOMAIN, expired certs, rate limits).

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?

The purpose statement is front-loaded in the first clause, and the pricing/demo details are short and actionable. There is mild redundancy in listing the record types and certificate fields twice across the two sentences, but the enumeration earns its place because no output schema documents the response shape.

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

Completeness4/5

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

For a one-parameter read-only tool with no output schema, the description covers scope (public domains), cost model, and expected return fields, which is close to what an agent needs to call it confidently. The remaining gap is error and edge-case behavior, but that is secondary for a simple lookup.

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 coverage is 100% for the single 'domain' parameter, including the maxLength and the 'no scheme, no path' format guidance, so the schema already does the heavy lifting. The description's only added constraint is that the domain must be public, which is useful but minimal. 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?

The description names a specific verb and resource ('Check DNS records and SSL certificate of a domain') and enumerates exactly what is inspected: A, AAAA, CNAME, MX, NS, TXT, CAA records plus live TLS issuer, validity, days left, SANs, protocol, and trust. This is well differentiated from the sibling crypto/text/web tools, which operate on entirely different resources.

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 implied rather than stated: 'of a public domain' signals the tool only works against public DNS, and the price line signals when the paid endpoint applies. However, there is no explicit when-to-use/when-not-to-use guidance, no mention of alternatives such as the general web_meta tool, and no note on what happens for internal or non-resolvable domains.

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.

Resources