Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_compliance_ssl_cert_inspector

Inspect a domain's certificate issuance history via Certificate Transparency logs to verify compliance and assess trust.

Instructions

[Compliance & Trust] Inspect certificate issuance history via Certificate Transparency Measured p50 12 ms, p95 16 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://compliance.caelaralabs.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": {
      "domain": "<domain>"
    },
    "name": "caelara_compliance_ssl_cert_inspector"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It reveals the backing endpoint and latency figures but says nothing about return content, whether the call is read-only, rate limits, or how wildcard/subdomain certificates are handled.

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?

Front-loaded with a category tag and a clear purpose clause, which is good structure. However, the benchmark latency figures and provenance URL consume roughly half the text without helping an agent decide or invoke correctly.

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

Completeness2/5

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

For a read-only lookup with no annotations and no output schema, the description should indicate what comes back (issuance entries, issuers, date ranges). It does not, leaving the agent unable to anticipate the response shape.

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% for the single required `domain` parameter, so the schema already documents it. The description adds no format guidance (bare domain vs. URL vs. subdomain), so baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource: "Inspect certificate issuance history via Certificate Transparency." That is concrete enough to distinguish the purpose from sibling compliance tools like SPF/DMARC grading or IBAN validation. It does not explicitly name an alternative, but the resource is unambiguous.

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

Usage Guidelines2/5

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

No guidance on when to use this versus the other compliance inspectors (e.g., domain_trust_composite or security_headers_audit), no prerequisites, and no exclusions. The only implicit usage signal is the tool's own subject matter.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools