Skip to main content
Glama

x420_tls_certificate

Check a public host’s TLS certificate to verify its issuer, domain coverage, validity, expiration, chain trust, protocol, and cipher, helping identify expired or misconfigured certificates.

Instructions

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. PAID: $0.03 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: subject, issuer, sans[], valid_from, valid_to, days_remaining, expired, authorized, covers_host, protocol, cipher - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"host":"example.com"}.

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 observedv1.0.2

TDQS

A3.9/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing real-money cost ($0.03 USDC on Base), the required wallet credential (X420_MCP_WALLET_PRIVATE_KEY), and that each call produces a signed receipt and settlement transaction. It does not state rate limits or failure behavior for unreachable hosts, but the payment and auth disclosures are substantive and consistent with readOnlyHint=false (payment side effect) and openWorldHint=true.

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?

Front-loaded with the purpose and result fields, then cost, then return shape, then an example – a sensible ordering with no ambiguity. The legal disclaimer boilerplate ('Not professional, legal... advice') is one sentence of pure noise that keeps it from a 5.

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 2-parameter read-style tool with no output schema, the description supplies the field list, cost, credential requirement, and an example, which is nearly everything an agent needs. Missing only error/failure semantics for hosts that do not respond to a handshake.

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 ('public hostname') and port ('default 443') documented inline, so the baseline is 3. The description only adds a concrete example input and the 'public' constraint on host, which is marginal but not redundant.

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?

States a specific verb and resource ('connects to a public host and reports the presented TLS certificate') plus the exact field set returned, which distinguishes it from siblings like dns_lookup or http_endpoint-check. An agent knows immediately this is a live handshake inspection, not a DNS or reachability probe.

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?

Gives useful context ('Source: direct handshake', 'public host', paid per call), which implies when it applies, but never states when a sibling should be preferred or what conditions disqualify it (private hosts, IP-only targets, non-443 ports). Usage 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.