Skip to main content
Glama
rosschurchill

Technitium MCP Secure

dns_health_check

Check DNS server health by retrieving version, uptime, forwarder configuration, blocking status, and last hour failure rate.

Instructions

Quick health check of the DNS server. Returns version, uptime, forwarder config, blocking status, and last hour failure rate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for dns_health_check. It concurrently fetches server settings and last-hour dashboard stats, computes the failure rate, and returns a JSON object with version, uptime, forwarder config, blocking status, and last-hour query stats.
    handler: async () => {
      const [settings, stats] = await Promise.all([
        client.callOrThrow("/api/settings/get"),
        client.callOrThrow("/api/dashboard/stats/get", {
          type: "LastHour",
        }),
      ]);
    
      const s = stats.stats as Record<string, number>;
      const totalQueries = s.totalQueries || 0;
      const failures = s.totalServerFailure || 0;
      const failureRate =
        totalQueries > 0
          ? ((failures / totalQueries) * 100).toFixed(1)
          : "0.0";
    
      return JSON.stringify(
        {
          version: settings.version,
          uptimestamp: settings.uptimestamp,
          dnsServerDomain: settings.dnsServerDomain,
          forwarders: settings.forwarders,
          forwarderProtocol: settings.forwarderProtocol,
          enableBlocking: settings.enableBlocking,
          lastHour: {
            totalQueries,
            serverFailures: failures,
            failureRate: `${failureRate}%`,
            blocked: s.totalBlocked || 0,
            cached: s.totalCached || 0,
          },
        },
        null,
        2
      );
    },
  • Schema definition for dns_health_check tool. It has an empty input schema (no parameters) and a description explaining it returns version, uptime, forwarder config, blocking status, and failure rate.
    {
      definition: {
        name: "dns_health_check",
        description:
          "Quick health check of the DNS server. Returns version, uptime, forwarder config, blocking status, and last hour failure rate.",
        inputSchema: {
          type: "object",
          properties: {},
        },
      },
  • The tool is registered via dashboardTools() in src/tools/index.ts, which is called by getAllTools() and aggregated into the toolMap in src/index.ts where it's served to the MCP client.
    export function getAllTools(client: TechnitiumClient): ToolEntry[] {
      return [
        ...dashboardTools(client),
        ...dnsClientTools(client),
        ...zoneTools(client),
        ...recordTools(client),
        ...blockingTools(client),
        ...cacheTools(client),
        ...settingsTools(client),
        ...logTools(client),
        ...appTools(client),
        ...dnssecTools(client),
      ];
  • The validatePeriod helper is imported by dashboard.ts and used by dns_get_stats (the sibling tool in the same file). dns_health_check does not directly use it, but it's imported and available.
    export function validatePeriod(period: string): string {
      if (!VALID_PERIODS.has(period)) {
        throw new Error(`Invalid period: ${period}. Valid: ${[...VALID_PERIODS].join(", ")}`);
      }
      return period;
    }
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It lists the returned data (version, uptime, etc.) but does not explicitly state read-only behavior or potential side effects, though a health check is implicitly non-destructive.

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 a single sentence with no wasted words, front-loading the purpose and listing the returned fields efficiently.

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?

Given the tool's simplicity (no parameters, no output schema), the description fully covers its purpose and output, making it complete for an agent to select and invoke.

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?

The tool has zero parameters with 100% schema coverage (empty schema). The description does not need to add parameter details; the baseline score of 4 is appropriate.

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 states a specific verb ('Quick health check') and clearly lists what it returns (version, uptime, etc.), differentiating it from sibling tools that focus on DNS management tasks like adding records or zones.

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

Usage Guidelines4/5

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

The description explicitly says 'quick health check', signaling when to use this tool. While it does not mention when not to use it or provide alternatives, the context among sibling tools makes its purpose clear.

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