Skip to main content
Glama
rosschurchill

Technitium MCP Secure

dns_get_app_config

Retrieve configuration for an installed DNS app by providing its name.

Instructions

Get the configuration for an installed DNS app.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the installed app

Implementation Reference

  • The handler function for the dns_get_app_config tool. It validates the 'name' parameter, calls the Technitium API endpoint /api/apps/config/get with the app name, and returns the configuration as a JSON string.
    {
      definition: {
        name: "dns_get_app_config",
        description:
          "Get the configuration for an installed DNS app.",
        inputSchema: {
          type: "object",
          properties: {
            name: {
              type: "string",
              description: "Name of the installed app",
            },
          },
          required: ["name"],
        },
      },
      readonly: true,
      handler: async (args) => {
        const name = validateStringLength(args.name as string, 200, "App name");
        const data = await client.callOrThrow("/api/apps/config/get", { name });
        return JSON.stringify(data, null, 2);
      },
    },
  • The input schema for dns_get_app_config defines a single required parameter 'name' (type string) which is the name of the installed app whose configuration is to be retrieved.
    {
      definition: {
        name: "dns_get_app_config",
        description:
          "Get the configuration for an installed DNS app.",
        inputSchema: {
          type: "object",
          properties: {
            name: {
              type: "string",
              description: "Name of the installed app",
            },
          },
          required: ["name"],
        },
      },
      readonly: true,
      handler: async (args) => {
        const name = validateStringLength(args.name as string, 200, "App name");
        const data = await client.callOrThrow("/api/apps/config/get", { name });
        return JSON.stringify(data, null, 2);
      },
    },
  • The dns_get_app_config tool is registered as part of the appTools function (line 5) which returns an array of ToolEntry objects. This is aggregated into all tools via getAllTools in src/tools/index.ts (line 24), which is used in the MCP server setup in src/index.ts (line 21-26).
    import { TechnitiumClient } from "../client.js";
    import { ToolEntry } from "../types.js";
    import { validateStringLength } from "../validate.js";
    
    export function appTools(client: TechnitiumClient): ToolEntry[] {
      return [
        {
          definition: {
            name: "dns_list_apps",
            description:
              "List installed DNS apps on the server and their current status.",
            inputSchema: {
              type: "object",
              properties: {},
            },
          },
          readonly: true,
          handler: async () => {
            const data = await client.callOrThrow("/api/apps/list");
            return JSON.stringify(data, null, 2);
          },
        },
        {
          definition: {
            name: "dns_list_app_store",
            description:
              "List all available apps from the Technitium DNS app store with versions and descriptions.",
            inputSchema: {
              type: "object",
              properties: {},
            },
          },
          readonly: true,
          handler: async () => {
            const data = await client.callOrThrow("/api/apps/listStoreApps");
            return JSON.stringify(data, null, 2);
          },
        },
        {
          definition: {
            name: "dns_install_app",
            description:
              "Download and install a DNS app from the Technitium app store. Use dns_list_app_store to see available apps.",
            inputSchema: {
              type: "object",
              properties: {
                name: {
                  type: "string",
                  description:
                    "App name exactly as shown in the app store (e.g. 'Query Logs (Sqlite)')",
                },
              },
              required: ["name"],
            },
          },
          readonly: false,
          handler: async (args) => {
            const name = validateStringLength(args.name as string, 200, "App name");
            const data = await client.callOrThrow(
              "/api/apps/downloadAndInstall",
              { name }
            );
            return JSON.stringify(
              { success: true, installed: name, ...data },
              null,
              2
            );
          },
        },
        {
          definition: {
            name: "dns_uninstall_app",
            description:
              "Uninstall a DNS app from the server. Requires confirm=true to execute.",
            inputSchema: {
              type: "object",
              properties: {
                name: {
                  type: "string",
                  description: "Name of the app to uninstall",
                },
                confirm: {
                  type: "boolean",
                  description:
                    "Must be true to confirm uninstall. Without this, returns a warning instead.",
                },
              },
              required: ["name"],
            },
          },
          readonly: false,
          handler: async (args) => {
            const name = validateStringLength(args.name as string, 200, "App name");
            if (args.confirm !== true) {
              return JSON.stringify(
                {
                  warning: `This will uninstall the app '${name}' and remove its data. Set confirm=true to proceed.`,
                },
                null,
                2
              );
            }
            const data = await client.callOrThrow("/api/apps/uninstall", { name });
            return JSON.stringify(
              { success: true, uninstalled: name, ...data },
              null,
              2
            );
          },
        },
        {
          definition: {
            name: "dns_get_app_config",
            description:
              "Get the configuration for an installed DNS app.",
            inputSchema: {
              type: "object",
              properties: {
                name: {
                  type: "string",
                  description: "Name of the installed app",
                },
              },
              required: ["name"],
            },
          },
          readonly: true,
          handler: async (args) => {
            const name = validateStringLength(args.name as string, 200, "App name");
            const data = await client.callOrThrow("/api/apps/config/get", { name });
            return JSON.stringify(data, null, 2);
          },
        },
      ];
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

B3.3/5.0
Behavior2/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 of behavioral disclosure. It merely states 'Get the configuration' without mentioning permissions, side effects, return format, or any prerequisites such as the app being installed. This is minimal but not misleading.

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 one concise sentence with no filler. It is appropriately front-loaded and easily parsed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with a single parameter and no output schema, so the description is minimally adequate. However, it lacks any detail about what the configuration contains or how to interpret the result, which would be helpful given no annotations or output schema.

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 description coverage is 100% (the 'name' parameter is described as 'Name of the installed app'). The tool description adds no additional meaning beyond the schema, so it meets the baseline but does not improve on it.

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 'configuration for an installed DNS app'. It is specific and distinguishes itself from siblings like dns_list_apps (which lists apps) by focusing on retrieving configuration for a single app.

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?

The description provides no guidance on when to use this tool versus alternatives. There are many sibling tools (e.g., dns_install_app, dns_list_apps), but no mention of when this tool is appropriate or when a different tool should be used instead.

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