Skip to main content
Glama

LexGrid — NetSec, Deliverability & RDAP

tls_http_inspector

Read-onlyIdempotent

[Live TLS socket inspection. Read-only, non-destructive, side-effect free]. Connects to target host port (default 443) to inspect X.509 certificate validity and expiration, Subject Alternative Names (SANs), TLS protocol version (TLS 1.2/1.3), cipher suite strength, HTTP security headers (HSTS, CSP, X-Frame-Options), and /.well-known/security.txt. Usage: Use this tool to assess web transport security and HTTPS certificate health. For domain ownership age, use 'domain_rdap_intel'. For exposed internal ports, use 'port_leak_detector'. Returns: JSON object with { hostname: string, port: number, certificate: { valid: boolean, daysUntilExpiration: number, issuer: string, sans: string[] }, tlsVersion: string, cipherSuite: string, securityHeaders: { hsts: boolean, csp: boolean, xfo: boolean }, securityTxtFound: boolean, securityScore: number }.

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": {
      "hostname": "<hostname>"
    },
    "name": "tls_http_inspector"
  }
}

Input Schema

NameRequiredDescriptionDefault
portNoPort number (default 443)
hostnameYesDomain or hostname to inspect (e.g. novapixel.it)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces this with 'non-destructive, side-effect free' while adding that this is a live socket connection to the target host. It also discloses the full result shape (cert fields, securityScore) despite having no output schema. The remaining gap is operational behavior: no mention of timeouts, reachability failures, or rate limits on repeated live connections.

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?

Well front-loaded with a bracketed tag line, then clear Usage and Returns sections; every block serves a purpose. Minor waste in the triple-redundant 'Read-only, non-destructive, side-effect free', which largely repeats the annotations.

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 two-parameter tool with no output schema, the description carries the return contract explicitly, including nested certificate fields and a computed securityScore. Only failure modes (unreachable host, TLS handshake errors) and whether private/internal addresses are permitted are left unaddressed.

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% (both `hostname` and `port` are documented in the schema), so the baseline is 3. The description restates the default port 443 but adds no syntax, format, or edge-case meaning beyond what the schema already provides.

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?

The description names a specific verb and resource ('Connects to target host port ... to inspect X.509 certificate validity and expiration, SANs, TLS protocol version, cipher suite strength, HTTP security headers, security.txt'). It also implicitly separates itself from the sibling tools by scoping itself to transport/certificate inspection.

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?

It gives an explicit usage line ('Use this tool to assess web transport security and HTTPS certificate health') and names two alternatives with the conditions that select them ('domain ownership age' -> domain_rdap_intel, 'exposed internal ports' -> port_leak_detector). The routing decision is unambiguous.

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