Skip to main content
Glama
rosschurchill

Technitium MCP Secure

dns_uninstall_app

Uninstall a DNS app from the server by specifying its name and setting confirm to true to execute the removal.

Instructions

Uninstall a DNS app from the server. Requires confirm=true to execute.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the app to uninstall
confirmNoMust be true to confirm uninstall. Without this, returns a warning instead.

Implementation Reference

  • The handler function for dns_uninstall_app tool. It validates the app name length, checks for confirm=true (returning a warning if not confirmed), then calls the API endpoint /api/apps/uninstall to uninstall the app.
    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
      );
    },
  • The input schema for dns_uninstall_app. Defines required 'name' (string) and optional 'confirm' (boolean) parameters. Used for input validation.
    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"],
      },
  • src/tools/apps.ts:5-6 (registration)
    The appTools() function that returns an array of tool entries, including dns_uninstall_app. This is called from getAllTools() in src/tools/index.ts.
    export function appTools(client: TechnitiumClient): ToolEntry[] {
      return [
  • The getAllTools() function that aggregates all tool collections from various modules, including appTools() which contains dns_uninstall_app.
    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 validateStringLength helper used by the handler to validate the 'name' parameter length.
    export function validateStringLength(value: string, maxLength: number, fieldName: string): string {
      if (typeof value !== "string") {
        throw new Error(`${fieldName} must be a string`);
      }
      if (value.length > maxLength) {
        throw new Error(`${fieldName} exceeds maximum length of ${maxLength}`);
      }
      return value;
    }
Behavior2/5

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

No annotations provided; description mentions uninstall and confirm guard but lacks details on side effects, reversibility, or auth needs.

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?

Two concise sentences, front-loaded with the core action, no wasted words.

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?

Covers the essential for a simple tool but omits return value and error handling; adequate but not comprehensive.

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 100%; description confirms the confirm parameter's role but adds no new meaning beyond the schema.

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 action (uninstall) and the resource (DNS app), distinguishing it from siblings like install and config tools.

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?

It highlights the confirm parameter requirement, guiding usage, but does not explicitly mention when not to use or alternatives.

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