Skip to main content
Glama

RenewRoster

Certificate Transparency lookup

lookup_ct
Read-onlyIdempotent

Latest certificate for a hostname from public CT logs (not saved; does not contact the host).

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

Input Schema

NameRequiredDescriptionDefault
hostYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 the safety profile is covered. The description adds genuinely new behavioral facts: results are not persisted and the target host is not contacted (no active probing), which matter for an open-world lookup. It stops short of saying what happens when no certificate is found.

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?

One sentence with the core action front-loaded and the scoping caveats in a tight parenthetical. No filler, nothing redundant.

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 one-parameter, read-only lookup with full annotation coverage and no output schema, the description covers source of truth and side-effect profile adequately. Minor gaps remain around empty-result behavior and what certificate fields come back, but nothing blocks a correct call.

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 0% and the single 'host' parameter carries no description or format in the schema. The description compensates partially by identifying the input as a hostname (not a URL, IP, or domain object), but adds no detail on format, wildcard handling, or subdomain semantics.

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: fetch the latest certificate for a hostname from public CT logs. The parenthetical clarifies the scope ('not saved; does not contact the host'). However, it never distinguishes itself from the sibling 'lookup_cert', which reads like a near-identical certificate lookup, leaving the agent to guess which one to pick.

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 only implied: 'public CT logs (not saved; does not contact the host)' hints that this is a passive external query rather than an inventory lookup, which weakly separates it from lookup_cert/lookup_domain. There is no explicit when-to-use, when-not, or named alternative, so routing still requires inference.

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.