Skip to main content
Glama

Tls cert

tls_cert
Read-onlyIdempotent

Inspect live TLS certificate chain, validity/expiry days left, SANs, protocol, cipher, and trust store verification. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
hostYespublic hostname, no scheme or path
portNo443 (default) or 8443
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so safety and side-effect behavior are covered. The description adds genuinely useful context the annotations cannot carry: the per-call price, accepted payment rails, and the fact that a second call is required to complete a purchase. It says nothing about network timeouts, failure modes against unreachable hosts, or rate limits on live inspection.

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?

Two sentences, front-loaded with what gets inspected, followed by the payment mechanics. The currency list (USDC on Arc, Base or Solana, or XNT on X1) is dense but necessary for the agent to know what payment to construct, so little is wasted.

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?

There is no output schema, and the description compensates by enumerating the returned certificate fields. It also explains the two-phase payment flow, which is essential for this tool to complete at all. Missing only failure/timeout behavior for unreachable or non-TLS hosts.

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 host and port are already documented in the schema, and enum-free port options are spelled out there. The description restates the payment parameter's purpose ('call again with `payment`') but adds only the workflow framing, not new syntax or format detail beyond the schema.

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?

States a specific verb and resource plus the exact fields returned: chain, validity/expiry days left, SANs, protocol, cipher, and trust-store verification. That field list distinguishes it from siblings like security_headers or dns_records without the agent needing to open any schema.

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

Usage Guidelines4/5

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

The payment sentence gives concrete two-step invocation guidance: call once without `payment` to get the terms, sign with your own wallet, call again with the payload. It does not say when to prefer this tool over security_headers or url_status for broader site checks, so it stops short of explicit alternatives.

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