Skip to main content
Glama

X420 agent services

x420_tls_certificate

Read-onlyIdempotent

TLS certificate check: Connects to a public host and reports the presented TLS certificate: subject, issuer, SANs, validity window, days remaining, chain trust, protocol and cipher. Source: direct handshake. Not professional, legal, insurance, engineering, medical, financial or tax advice. Price: $0.03 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: subject, issuer, sans[], valid_from, valid_to, days_remaining, expired, authorized, covers_host, protocol, cipher.

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": {
      "host": "<host>"
    },
    "name": "x420_tls_certificate"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYespublic hostname
portNoTCP port (default 443)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), the description discloses the critical non-obvious behavior that the hosted tool does NOT pay and does NOT return the deliverable, instead returning pay_to, network, price and the x402 URL. It also states the price ($0.03 USDC on Base) and the exact 402 retry protocol, which an agent could not infer from annotations or schema.

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 purpose and payment mechanics are front-loaded, which is good, but the sentence 'Not professional, legal, insurance, engineering, medical, financial or tax advice' is boilerplate that does not help an agent decide or invoke. The payment paragraph is dense but earns its space, while the deliverable field list partially duplicates what the purpose sentence already implies.

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?

With no output schema, the description compensates by listing the deliverable JSON keys (sans[], valid_from, valid_to, days_remaining, expired, authorized, covers_host, protocol, cipher), which is sufficient for an agent to know what comes back after payment. Minor gaps remain, such as behavior on handshake failure or unreachable/invalid hosts, but the definition is complete enough for correct invocation.

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%, with both 'host' and 'port' (default 443) documented in the schema itself. The description only implicitly reinforces that the host must be public and reachable via a direct handshake, adding little parameter-level meaning beyond the schema, so the baseline of 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 gives a specific verb and resource ('Connects to a public host and reports the presented TLS certificate') and enumerates what is reported (subject, issuer, SANs, validity window, days remaining, chain trust, protocol, cipher). This separates it cleanly from siblings such as x420_http_endpoint-check or x420_domain_rdap, which do not read the live certificate from a handshake.

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?

The description explains the payment flow (GET the url, read PAYMENT-REQUIRED, retry with PAYMENT-SIGNATURE, or run the local x420-mcp server) which is actionable operational guidance. However it never states when to choose this over related tools in the catalog (http endpoint check, domain RDAP, sitescan) or any exclusion such as private/internal hosts remaining unstated despite 'public hostname' in the schema.

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