Skip to main content
Glama

SSL Certificate Expiry Payment Quote

domain_ssl_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/domain/ssl (base $0.005; 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 hostname per call). To check a host's TLS certificate: one direct handshake on port 443 returns issuer, subject, SANs, valid from/to, days remaining, expired, hostname match, chain length and chain validation as observed, plus protocol. Input: one public hostname, one name per call. No HTTP request is sent. Errors are 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": "domain_ssl_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive, non-open-world. The description does add genuine value beyond them: flat $0.005 pricing, no HTTP request sent, and settlement/refund rules by chain. That value is undercut by noise and incoherence — it discusses Solana and XRP Ledger settlement for chains not offered (only Base/Polygon are quoted) and repeats 'errors are not charged' in several reworded forms.

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 pricing/payment info that should lead is buried after the API URL, and the check-behavior paragraph is irrelevant to a quote tool. Settlement rules are restated three times with contradictory chain coverage, so the text is verbose without being clearer.

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 it does cover price, currency, chain options, and the x402 payment mechanism, which is the essential information. But the omission of the follow-up tool and the misleading input description leave the agent's workflow incomplete.

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?

With zero parameters the baseline would be 4, but the description asserts 'Input: one public hostname, one name per call,' which conflicts with the empty schema. An agent could try to supply a domain argument that does not exist, so the description actively adds confusion rather than meaning here.

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

Purpose3/5

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

The opening sentence is specific: it returns payment terms for the SSL check endpoint and explicitly 'never runs the check or pays.' However, most of the remaining text describes the behavior of the underlying TLS handshake check (issuer, SANs, chain validation, protocol), which this tool does not perform. An agent reading past the first sentence could easily mistake this for the checking tool.

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 states a negative boundary ('never runs the check or pays') and outlines the 402/x402 v2 payment flow, implying this is the pricing step before the real check. But it never names the sibling tool to invoke after payment, so the when-to-use guidance is implied rather than explicit.

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.