Skip to main content
Glama

Caelara Labs Compliance & Trust

ssl_cert_inspector

Inspect certificate issuance history via Certificate Transparency

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_cert_inspector"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose a meaningful behavioral fact: results come from Certificate Transparency logs, implying a passive, read-only lookup of publicly logged certificates rather than a live handshake. It omits whether the call is strictly read-only, how domains with no logged certificates are handled, and any rate-limit or latency expectations.

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 short sentence, front-loaded with the verb and resource, with zero filler. It is efficient, though the brevity leaves the gaps noted in other dimensions rather than being maximally informative.

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

Completeness3/5

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

For a simple one-parameter read tool with no output schema, the description covers purpose and data source adequately. It leaves the agent guessing about input formatting and result shape (a list of issuance events), which is a moderate gap given the tool has no annotations to fall back on.

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 description coverage is 100% for the single `domain` parameter, so the baseline of 3 applies. The description adds no format guidance beyond the schema — it does not say whether a bare domain, wildcard, URL, or subdomain form is expected, which is the one detail that would materially help.

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 ("Inspect"), a specific resource ("certificate issuance history"), and the underlying data source (Certificate Transparency). This clearly distinguishes it from siblings like security_headers_audit or domain_trust_composite, though it does not explicitly name or contrast with any of them.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. The agent must infer that this is the tool for certificate/log history rather than live TLS configuration, and nothing tells it whether to pair this with security_headers_audit or domain_trust_composite.

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