Skip to main content
Glama

RenewRoster

Check a host's SSL certificate

lookup_cert
Read-onlyIdempotent

Live TLS check of a public host's served certificate (not saved). Ports: 443, 8443, 465, 993, 995.

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

Input Schema

NameRequiredDescriptionDefault
hostYes
portNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is largely covered. The description still adds real value by clarifying the check is live against the served certificate and nothing is persisted, which tells the agent results are point-in-time and network-dependent. It stops short of covering timeout, DNS failure, or handshake-error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero filler, with the key qualifier (live, not saved) and the port constraint front-loaded. Nothing repeats the title or wastes tokens.

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 two-parameter lookup with no output schema, the definition is thin: it never says what the result contains (issuer, validity dates, SANs, chain), what the default port is, or how failures are surfaced. Annotations carry the safety profile, which keeps it at minimum viable rather than inadequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter meaning. The port enumeration is a genuine aid, but it is never stated whether port is optional, what the default is when omitted, or what 'host' accepts (bare hostname vs host:port vs URL), leaving a required parameter effectively undocumented.

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?

"Live TLS check of a public host's served certificate (not saved)" gives a specific verb plus resource and disambiguates a live fetch from stored-cert data. It doesn't explicitly contrast with the adjacent lookup_ct and lookup_domain siblings, so the agent must infer the boundary rather than being told.

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?

The port list (443, 8443, 465, 993, 995) implies the intended usage contexts (HTTPS, SMTPS, IMAPS, POP3S) and "not saved" hints at when to prefer this over a stored-asset lookup. However, there is no explicit statement of when to use this versus lookup_ct or lookup_domain, and no note on prerequisites or failure conditions.

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.