Skip to main content
Glama

AEGIS (McX Ventures)

TLS / SSL certificate check

tls_check
Read-only

TLS/SSL certificate check for one public host — issuer, validity and expiry, SANs, SHA-256 fingerprint, CA classification Price: $0.005 USDC on Base per call, paid with x402.

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": {
      "target": "<target>"
    },
    "name": "tls_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesPublic hostname or IP address, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds a materially important trait the annotations do not cover: the call costs $0.005 USDC on Base and is settled via x402, which an agent must know before invoking. It also lists the returned data, though it omits failure behavior for unresolvable or non-public hosts.

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?

Front-loaded with the purpose and return fields, no filler. The only flaw is the missing separator before "Price:", which splices the pricing clause onto the field list as a run-on.

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 correctly compensates by enumerating the returned certificate attributes, and it discloses the payment model. It stops short of noting error cases (invalid host, handshake failure) or any rate/throughput limits for a single-host tool.

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% and the single `target` parameter already documents "Public hostname or IP address, e.g. example.com". The description only adds the "one" cardinality constraint (no batching), which is a small increment over structured data — baseline 3.

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?

Names a specific verb+resource ("TLS/SSL certificate check for one public host") and enumerates exactly what the call returns (issuer, validity/expiry, SANs, SHA-256 fingerprint, CA classification). This makes it immediately distinguishable from certificate-transparency or DNS siblings without opening 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 Guidelines3/5

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

Usage is only implied by the phrase "one public host" — a single target per call, and that target must be publicly reachable. There is no explicit when-to-use versus when-not statement and no mention of an alternative tool for CT logs or DNS records.

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