Skip to main content
Glama

UAI x402 Security Tools

ssl-certificate-audit

Audit domain SSL/TLS certificate expiry, HTTPS reachability, HSTS, and HTTP-to-HTTPS redirect posture using certificate transparency and live transport checks. (REST equivalent: POST /api/v1/ssl-certificate-audit, $0.05)

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": {
      "domain": "<domain>"
    },
    "name": "ssl-certificate-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain to audit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations contain only a title, so the description carries the full behavioral burden. It does disclose meaningful context — that checks use certificate transparency and live transport checks (implying external network calls) and that the REST equivalent costs $0.05 — but it never states that the operation is read-only/non-destructive, nor does it cover rate limits, failure behavior, or auth requirements.

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?

Two sentences, fully front-loaded with the audit scope followed by methodology and the REST/pricing note. No filler, no redundancy — every clause adds information an agent can use.

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

Completeness3/5

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

For a single-parameter network audit tool with no output schema, the definition explains what will be checked and how, but omits any indication of what the results look like (pass/fail per check, certificate details, error handling for unreachable domains). That is a notable gap given there is no output schema to fall back on.

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% for the single 'domain' parameter, so the schema already carries the semantics and baseline 3 applies. The description adds nothing about expected domain format (bare hostname vs. scheme/port), which would have been the one useful addition for a single-param tool.

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 uses the specific verb 'Audit' with a precisely enumerated resource: certificate expiry, HTTPS reachability, HSTS, and HTTP-to-HTTPS redirect posture. It is clearly distinguishable from siblings like dns-email-security-audit or cloudflare-zero-trust-audit, which cover different security domains.

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 implied by the enumerated checks — an agent can infer this is the tool for auditing a domain's TLS posture. However, there is no explicit when-to-use guidance, no conditions under which to prefer or avoid this tool, and no named alternatives among the many sibling audit tools.

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