Skip to main content
Glama

Nalvorn Checks

tls_cert

Read-only

Certificate expiry, issuer and SAN coverage for a host, days left and verdict Costs 0.001 USDC per call on Base (x402). Call it over HTTP with a PAYMENT-SIGNATURE header to actually run it.

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
hostYesHost name without scheme, for example example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds genuinely non-obvious behavior: each call costs 0.001 USDC on Base via x402 and must be invoked over HTTP with a PAYMENT-SIGNATURE header to actually execute. That payment/auth requirement is exactly the kind of operational fact an agent would otherwise fail on, though the phrasing 'to actually run it' is slightly ambiguous about what happens without the header.

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 compact sentences that front-load the returned fields before the payment mechanics. Minor flaws: the first sentence runs on without punctuation between 'verdict' and 'Costs', and the x402/Base detail is dense, but nothing is 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?

With no output schema, the description carries the burden of describing returns and does so adequately by enumerating expiry, issuer, SAN coverage, days left, and verdict. The payment prerequisite is also covered, leaving only the ambiguity of what a call without the PAYMENT-SIGNATURE header returns.

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% and the single host parameter is documented with an example format (example.com, no scheme). The description adds no further parsing constraints or edge cases beyond what the schema already states, so the baseline of 3 applies.

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?

The description names the resource (a host's TLS certificate) and the specific data returned: expiry, issuer, SAN coverage, days left, and a verdict. That is far more concrete than a tautology, though it never distinguishes itself from plausible siblings like domain_posture or http_headers, which an agent may see as overlapping security checks.

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: an agent can infer this is the tool for checking certificate health of a single host. There is no explicit when-to-use versus when-not, and no mention of how it relates to domain_posture or full_report, so routing between the security-oriented siblings is left to 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.

Resources