Skip to main content
Glama

Lookproof DNS, mail and TLS security checks

DNSSEC check

dnssec
Read-onlyIdempotent

Use when the user asks whether a domain's DNS is secure or DNSSEC-signed, or why it fails on validating resolvers. Returns secure, insecure, bogus or unknown with DS and DNSKEY details. For name servers see nameservers, for certificate rules caa. Ex: 'Is the DNS of example.com secure?'. Free trial without an API key: a few calls a day.

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

Input Schema

NameRequiredDescriptionDefault
domainYesA public domain name, e.g. example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the description's job is lighter. It adds genuinely useful context beyond them: the four outcome states (secure/insecure/bogus/unknown), that DS and DNSKEY details are included, and the auth/rate-limit situation (free trial without an API key, a few calls a day). It stops short of explaining what each state implies for the caller.

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 usage trigger, then return values, then alternatives, then auth — a sensible ordering with no filler. The example query is somewhat redundant with the opening clause and is the one sentence that could be cut.

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 single-parameter, no-output-schema read tool, the definition covers purpose, alternatives, result states, and auth requirements. Minor gap: it names the four states without saying what distinguishes 'unknown' from 'insecure' for the agent's interpretation.

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?

Only one parameter and schema description coverage is 100%, with the schema already specifying 'a public domain name, e.g. example.com.' The description adds no further semantics about the domain argument, which is the expected baseline when the schema carries the load.

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+resource ('whether a domain's DNS is secure or DNSSEC-signed') and the diagnostic angle ('why it fails on validating resolvers'). It also explicitly distinguishes itself from siblings by naming nameservers and caa as the right tools for adjacent questions.

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?

Gives an explicit trigger condition (user asks about DNS security/DNSSEC status or validator failures) plus concrete routing to two alternatives. The example query 'Is the DNS of example.com secure?' anchors the trigger in real phrasing.

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.