Skip to main content
Glama
Sign In

Crtsh

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Crtsh Certificate

crtsh_certificate
Read-onlyIdempotent

"Show me certificate [crt.sh id]" / "get the PEM for cert [id]" / "which certificate has serial [hex]" — fetch one logged certificate from crt.sh by its crt.sh id or by its hex serial number. Returns the PEM body plus the logged metadata (issuer, common name, SANs, validity window). Use after crtsh_search_domain to pull the actual certificate for inspection, or to identify a certificate you only have a serial number for (e.g. from a CA revocation notice or a TLS error log).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "serial": "061610ef41aa5f79065c5fa4bb838dc6"
    },
    "name": "crtsh_certificate"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNocrt.sh certificate id, as returned in the "id" field by crtsh_search_domain.
serialNoCertificate serial number in hex, e.g. "06b6e2677b20b8aa16af09f498667be23ead". Either id or serial is required.
include_pemNoInclude the base64 PEM body. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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. The description adds value beyond them by disclosing the return shape: the PEM body plus logged metadata (issuer, common name, SANs, validity window). It does not mention rate limits or auth requirements, which keeps it short of 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?

Front-loads the three natural-language query phrasings, then the core verb+resource, then the routing guidance. Every sentence earns its place, though the three quoted phrasings are slightly repetitive for the same operation.

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

Completeness5/5

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

No output schema exists, and the description compensates by describing the returned PEM and metadata. Combined with the routing guidance and 100% schema coverage on a 3-parameter tool, nothing an agent needs to call it correctly is missing.

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%, so the schema already documents id, serial and include_pem. The description reinforces where the crt.sh id comes from and why a hex serial would be used, adding marginal meaning but no format or syntax beyond the schema. Baseline 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?

Specific verb+resource: fetch one certificate from crt.sh by id or hex serial. It explicitly distinguishes itself from the sibling crtsh_search_domain by positioning itself as the follow-up lookup that pulls the actual certificate.

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

Usage Guidelines5/5

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

Gives two explicit when-to-use conditions: after crtsh_search_domain to inspect the actual certificate, or when you only have a serial number from a CA revocation notice or TLS error log. No alternative-tool ambiguity is left for the agent to resolve.

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

All Crtsh toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources