Skip to main content
Glama

dnssec_status

Check whether a domain publishes DNSSEC DS and DNSKEY records, and report delegation, key presence, and algorithms; this verifies publication, not cryptographic validation.

Instructions

Inspect DNSSEC DS and DNSKEY publication for a domain.

Reports delegation/key presence and algorithms. This is a publication check, not cryptographic DNSSEC validation.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the key behavioral trait: it only checks whether DS/DNSKEY records are published and what algorithms they use, not cryptographic validity. That caveat prevents misinterpretation of results, though it says nothing about rate limits, failure modes, or how missing records are reported.

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?

Three short sentences, front-loaded with the action and resource, followed by what is returned and then the scope caveat. Nothing is redundant or padded.

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 read tool with no annotations and no output schema, the description covers purpose, reported contents, and an important scope limit. A brief note on what a negative result means would make it fully self-sufficient.

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 0% and the single parameter 'domain' is completely unlabeled, so the description's phrase 'for a domain' does add the needed meaning that a domain name is the input. It does not clarify accepted format (apex vs subdomain, IDN, trailing dot), which is the one thing an agent could get wrong 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?

Uses a specific verb+resource pair ('Inspect DNSSEC DS and DNSKEY publication for a domain') and names the concrete artifacts inspected, so an agent knows this is about record publication rather than general DNS resolution. It does not differentiate itself from the sibling dns_lookup by name, which keeps it from a 5.

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?

The closing caveat ('This is a publication check, not cryptographic DNSSEC validation') gives an implicit when-not boundary, which is useful. However, no alternative tool is named for when a domain needs actual signature validation or general record lookup, so routing still requires inference.

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