Skip to main content
Glama

Check a site's HTTPS setup

https_check
Read-only

Check a site's HTTPS setup: whether http:// redirects to https://, HSTS and preload readiness, final URL, and mixed content (insecure http:// scripts, styles, images or iframes on the https page). Fast (1-3 s). Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.002 per call (x402, USDC on Base).

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": {
      "url": "<url>"
    },
    "name": "https_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description goes beyond them by disclosing latency (1-3 s) and a concrete cost model (free 20 calls/day, then $0.002/call via x402 USDC on Base). That cost and rate-limit context materially affects invocation decisions and is not available in structured fields. It does not describe result format or limits of the mixed-content scan.

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?

Front-loaded with the purpose and the concrete checks, then two short sentences on speed and price. Every clause carries information an agent or caller needs; nothing is padding.

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 read-only, single-URL checker with full schema coverage, the description covers what is inspected and what it costs. The main remaining gap is the shape of the response (no output schema exists), so the agent cannot anticipate the result structure or whether failures are reported per-check.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by explaining the payment economics that contextualize the otherwise cryptic 'payment' parameter (per-call charge above the free tier, USDC on Base via x402). The 'url' parameter only restates 'Public http(s) URL' with no added constraints such as reachability requirements.

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 states a specific verb and resource (check a site's HTTPS setup) and enumerates the exact checks: http-to-https redirect, HSTS and preload readiness, final URL, and mixed content. That is far more concrete than a tautology. It does not, however, distinguish this from overlapping siblings such as redirects or security_headers, leaving the agent to infer the boundary.

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, so an agent can infer this is the tool for HTTPS/HSTS/mixed-content questions, and the pricing sentence implicitly frames it as a per-URL lookup. There is no explicit when-to-use guidance relative to redirects or security_headers, and no stated exclusions (e.g., private/intranet URLs).

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.