Skip to main content
Glama

BRAINIAC Email & Domain Intelligence

Inspect domain TLS

email-domain_tls-inspect

Connect to port 443 of a public address for the domain and read the certificate. Certificate transparency names come from public crt.sh results. No other port is contacted. Price $0.05 USDC. POST /api/v1/email-domain/tls-inspect. Unpaid calls return 402 and do not run.

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": "email-domain_tls-inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the exact network behavior (only port 443 is contacted), the data provenance (public crt.sh results), the cost ($0.05 USDC), and the failure mode (unpaid calls return 402 and do not run). It stops short of describing timeout behavior or how DNS-unresolvable domains are handled.

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?

Five short sentences, each carrying distinct operational information (method, scope, provenance, price, payment failure), with the core action front-loaded. No filler or repetition.

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 one-parameter tool with no output schema and no annotations, the description covers the important unknowns: what is contacted, where CT data comes from, cost, and payment gating. The main residual gap is the shape of the returned certificate data, which the agent must infer from 'read the certificate' and 'certificate transparency names'.

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?

There is a single required parameter ('domain') at 0% schema description coverage. The description implies a meaningful constraint — the domain must resolve to a public address — but adds no format, length, or normalization guidance beyond what the bare schema field allows.

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 concrete verb and resource: connect to port 443 of a public address for the domain and read the certificate, plus a secondary data source (crt.sh CT names). That is far more specific than the title alone, though it never explicitly distinguishes itself from siblings like reputation-signals or deliverability-report.

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 subject matter (TLS/certificate inspection). The line 'No other port is contacted' constrains scope, and 'public address' hints at applicability, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative sibling tool.

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