Skip to main content
Glama
rosschurchill

Technitium MCP Secure

dns_dnssec_info

Retrieve DNSSEC properties for a DNS zone, including signing status, key details, and algorithm information.

Instructions

Get DNSSEC properties for a zone including signing status, key details, and algorithm info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoneYesZone domain name

Implementation Reference

  • Handler function for the dns_dnssec_info tool. It validates the zone domain, calls the Technitium API endpoint /api/zones/dnssec/properties/get, and returns the DNSSEC properties as a JSON string.
    handler: async (args) => {
      const zone = validateDomain(args.zone as string);
      const data = await client.callOrThrow(
        "/api/zones/dnssec/properties/get",
        { zone }
      );
      return JSON.stringify(data, null, 2);
    },
  • Input schema for dns_dnssec_info. Defines a single required parameter 'zone' (string, the zone domain name).
      inputSchema: {
        type: "object",
        properties: {
          zone: {
            type: "string",
            description: "Zone domain name",
          },
        },
        required: ["zone"],
      },
    },
  • Registration of the tool with name 'dns_dnssec_info' within the dnssecTools array.
    name: "dns_dnssec_info",
  • The dnssecTools function is called from getAllTools to include all DNSSEC tools (including dns_dnssec_info) in the tool registry.
      ...dnssecTools(client),
    ];
  • src/index.ts:35-41 (registration)
    The tool map is built from all tools (including dns_dnssec_info) and used to handle incoming CallToolRequest messages.
    const toolMap = new Map(tools.map((t) => [t.definition.name, t]));
    const rateLimiter = new RateLimiter();
    
    const server = new Server(
      { name: "technitium-mcp", version: VERSION },
      { capabilities: { tools: {} } }
    );
Behavior2/5

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

No annotations provided; description does not disclose read-only nature, permissions, or side effects. Burdens description, which fails to add transparency.

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?

Single concise sentence covering purpose and key details with no extraneous words.

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?

Simple tool with one parameter; description adequately covers returned info (signing status, keys, algorithm). Lacks output format details but sufficient for low complexity.

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 100% with zone description 'Zone domain name'. Description adds no extra meaning beyond schema, earning baseline 3.

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?

The description clearly states the verb 'Get' and the resource 'DNSSEC properties for a zone', with specifics like signing status, key details, and algorithm info. It distinguishes from sibling tools like dns_list_zones or dns_get_ds.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives. Given many sibling tools, explicit usage context is missing.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rosschurchill/technitium-mcp-secure'

If you have feedback or need assistance with the MCP directory API, please join our Discord server