Skip to main content
Glama

DomainVet

SSL/TLS certificates from Certificate Transparency

ssl_certs
Read-onlyIdempotent

List unexpired TLS certificates issued for a domain from public Certificate Transparency logs (Cert Spotter, crt.sh fallback): issuer (Let's Encrypt, DigiCert...), names covered, validity window, latest expiry and days remaining. Note: shows issued certs, not necessarily the one being served.

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so safety and idempotency are covered. The description adds meaningful behavior beyond that: the primary and fallback data sources, that only unexpired certificates are returned, the fields included (issuer, names covered, validity window, latest expiry, days remaining), and the important caveat about issued vs. served certificates. It does not mention rate limits, authentication, pagination, or error behavior, which keeps it from a 5.

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 description is compact and front-loaded: the core action and source appear in the first sentence, and the caveat follows immediately. Every clause carries useful information, though the first sentence is dense and could be split for readability. It is appropriately sized for a simple read-only lookup tool.

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 simple read-only tool with no output schema, the description is nearly complete: it explains the data source, fallback behavior, returned fields, the unexpired filter, and the issued-vs-served caveat. Minor omissions such as pagination, wildcard handling, and error behavior are not critical given the tool's simplicity and the annotations covering safety.

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 only one parameter, 'domain,' and schema description coverage is 100%. The description says certificates are listed 'for a domain,' but adds no syntax or format details beyond the schema, such as whether subdomains or wildcards are supported. With high schema coverage and no extra parameter meaning, the baseline of 3 is appropriate.

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 opens with a specific verb and resource: 'List unexpired TLS certificates issued for a domain from public Certificate Transparency logs.' It also names the data sources (Cert Spotter, crt.sh fallback) and lists the fields returned, making the tool clearly distinguishable from siblings such as dns_lookup or security_headers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context for when this tool is appropriate by stating it pulls issued certificates from CT logs and explicitly warns that it shows issued certs, 'not necessarily the one being served.' That caveat helps an agent decide against using it as a live-certificate checker. It does not name an alternative live-cert tool or give explicit when-not-to-use guidance beyond the caveat, so it falls short of a 5.

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