Skip to main content
Glama

List a domain's TLS certificates from CT logs

certs
Read-only

Current TLS certificates for a domain from Certificate Transparency logs (via CertSpotter): issuer, validity dates and days left, DNS names (up to 100 per certificate), and the distinct subdomains seen. Keyless tier: one request per call; answers are cached an hour. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "certs"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name, e.g. example.com

Output Schema

NameRequiredDescriptionDefault
domainNo
sourceNo
currentNo
checkedAtNo
issuancesNo
subdomainsNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely new operational context: one request per call, one-hour caching of answers, per-call pricing of $0.002 charged only on success, and the payment rails (x402, USDC on Base/Solana and 10 more networks). Failed calls not being charged and the caching window materially change how an agent should plan calls, none of which is in the annotations.

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?

One front-loaded paragraph that leads with the resource and source, then limits, then cost. Every sentence carries information, though the pricing/payment-network enumeration is slightly longer than an agent strictly needs to select the tool.

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

Completeness5/5

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

For a single-parameter read tool with an output schema present, the description covers what is returned, the data source, per-call request semantics, caching, and cost. Nothing an agent needs before calling (including the fact that calls are billable) is missing.

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?

There is a single 'domain' parameter with 100% schema description coverage, so the schema already carries its meaning. The description only restates 'for a domain' and adds no format, normalization, or scope constraints beyond the schema, so baseline 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?

Names a specific verb-resource pair ('Current TLS certificates for a domain') plus the data source (Certificate Transparency via CertSpotter), and enumerates the returned fields (issuer, validity, days left, DNS names, distinct subdomains). An agent can distinguish this from sibling tools like 'domain', 'dns' or 'subdomains' because it is explicitly about certificate records rather than DNS records or subdomain enumeration.

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 by the resource framing (use it when you need a domain's certificates) but there is no explicit when-to-use/when-not guidance and no named alternative for overlapping needs such as 'subdomains', which the description mentions as a by-product ('distinct subdomains seen'). The agent must infer the boundary itself.

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