Skip to main content
Glama

Check TLSA/DANE records

check_tlsa_dane
Read-onlyIdempotent

Read-only TLSA/DANE DNS record check. With no port, resolves MX hosts and validates their _25._tcp TLSA tuple syntax; with an explicit port, queries _<port>._<protocol>.<domain>.

Instructions

Read-only TLSA/DANE DNS record check. With no port, resolves MX hosts and validates their _25._tcp TLSA tuple syntax; with an explicit port, queries _<port>._<protocol>.<domain>. Returns parsed usage, selector, matching type, certificate data, syntax errors, and best-practice advisories. It does not fetch or cryptographically match the live service certificate, so pair it with check_smtp_tls for SMTP certificate evidence. Use before publishing DANE records or troubleshooting DANE handover. No auth or destructive actions.

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": "check_tlsa_dane"
  }
}

Input Schema

NameRequiredDescriptionDefault
portNoPort to check, defaults to 25
domainYesDomain name only, e.g. example.com (no URL, path, or port)
protocolNoTransport protocoltcp

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.10.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / domain / description
      Previous value: -"Domain name, e.g. example.com"New value: +"Domain name only, e.g. example.com (no URL, path, or port)"
    • addedInput schema / properties / domain / maxLength
      Added value: +253
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, but the description adds substantial context beyond them: default behavior resolves MX hosts and validates `_25._tcp` tuples, explicit ports switch query construction, and the tool returns parsed fields plus advisories. The limitation about not fetching or matching live certificates is exactly the kind of behavioral caveat an agent needs.

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?

The description is dense but front-loaded and wastes no sentences. Each sentence contributes either scope, mode behavior, return fields, a limitation, or a routing recommendation.

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

Completeness5/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 still names the returned data (usage, selector, matching type, certificate data, syntax errors, advisories). Combined with annotations covering safety and the schema covering parameters, the definition gives an agent enough to call it correctly and interpret the result.

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 schema already documents all three parameters. The description still adds operational meaning for `port` by explaining the no-port MX-host behavior versus explicit `_<port>._<protocol>.<domain>` querying, though it says less about `protocol` beyond the schema enum.

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?

States a specific verb and resource (read-only TLSA/DANE DNS record check) and immediately explains the two operating modes: default MX-host `_25._tcp` validation versus explicit-port queries. An agent can distinguish this from generation or SMTP TLS checks without inspecting the schema.

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

Usage Guidelines5/5

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

Explicitly names use cases (before publishing DANE records, troubleshooting DANE handover) and an alternative/complementary tool (`check_smtp_tls`) for live SMTP certificate evidence. It also clarifies the important limitation that this tool does not fetch or cryptographically match the live service certificate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.