Skip to main content
Glama

AEGIS (McX Ventures)

Certificate Transparency check

ct_check
Read-only

Certificate Transparency check for one domain — the live certificate's embedded SCTs verified against the known CT log list Price: $0.003 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": "ct_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesPublic hostname (not an IP address), e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations cover read-only and open-world behavior, and the description adds material context on top: the operation inspects a live (real-time) certificate and costs $0.003 USDC on Base via x402. Cost and payment mechanism are exactly the kind of behavioral fact the annotations do not carry. It stops short of describing failure modes such as a certificate with no SCTs.

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?

One front-loaded sentence covering what is checked and what it is checked against. The price clause is tacked onto the same sentence and reads slightly awkwardly, but nothing is wasted.

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?

There is no output schema, so the description should say what a caller gets back (pass/fail, the SCT list, log names) and what happens when no SCTs are present. It leaves that entirely open, though annotations and the price note do cover the safety and cost dimensions.

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 schema itself spells out 'public hostname, not an IP address' with an example. The description only restates the single-domain scope, adding essentially nothing beyond the schema, which is the expected baseline here.

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 a specific verb and resource: it verifies a live certificate's embedded SCTs against the known CT log list for a single domain. That is concrete enough to separate it from a generic TLS or DNS check, although it never names those siblings or states the contrast explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

'For one domain' implies the single-host scope, but there is no statement about when to run this instead of tls_check or dns_check, no prerequisites, and no exclusions beyond what the schema already says about IP addresses. An agent has to guess the routing.

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