dnssec
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_dnssec_chainB | Performs recursive cryptographic chain of trust validation (Root -> TLD -> Domain) for DNSSEC. |
| audit_dnssec_recordsB | Inspects and audits DNSKEY, DS, and RRSIG signature expiration and cipher strength. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one validates the full chain of trust, the other audits specific record types and their properties. There is no meaningful overlap or ambiguity between them.
Both tools follow a consistent verb_noun pattern (verify_dnssec_chain, audit_dnssec_records), making the naming predictable and easy to reason about.
Two tools is on the thin side for a general 'dnssec' server, though both are substantive and serve a focused read-only verification/audit purpose. The count feels borderline but justifiable.
The tools cover DNSKEY/DS/RRSIG auditing and chain validation, but the server lacks other common DNSSEC operations like signing, key generation, or record retrieval. Notable gaps exist for broader DNSSEC management, though the read-only validation workflow is reasonably covered.