Skip to main content
Glama
rosschurchill

Technitium MCP Secure

dns_flush_cache

Flush the entire DNS cache to clear all stored records, forcing fresh resolution from upstream servers. Requires confirmation before executing.

Instructions

Flush the entire DNS cache. Forces all subsequent queries to be resolved fresh from upstream. Requires confirm=true to execute.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust be true to confirm cache flush. Without this, returns a warning instead.

Implementation Reference

  • The handler function for the dns_flush_cache tool. Requires confirm=true to proceed, then calls the Technitium API /api/cache/flush endpoint to flush the DNS cache.
    handler: async (args) => {
      if (args.confirm !== true) {
        return JSON.stringify(
          {
            warning:
              "This will flush the entire DNS cache. All subsequent queries will be resolved fresh from upstream, which may temporarily increase latency. Set confirm=true to proceed.",
          },
          null,
          2
        );
      }
      const data = await client.callOrThrow("/api/cache/flush");
      return JSON.stringify(
        { success: true, message: "Cache flushed", ...data },
        null,
        2
      );
    },
  • The tool definition/schema including name, description, and inputSchema (confirm boolean).
    definition: {
      name: "dns_flush_cache",
      description:
        "Flush the entire DNS cache. Forces all subsequent queries to be resolved fresh from upstream. Requires confirm=true to execute.",
      inputSchema: {
        type: "object",
        properties: {
          confirm: {
            type: "boolean",
            description:
              "Must be true to confirm cache flush. Without this, returns a warning instead.",
          },
        },
      },
    },
  • src/tools/cache.ts:5-5 (registration)
    The dns_flush_cache tool is registered as part of the cacheTools array export, which is imported by src/tools/index.ts (line 8) and aggregated into getAllTools() for the MCP server.
    export function cacheTools(client: TechnitiumClient): ToolEntry[] {
  • The helper method callOrThrow on TechnitiumClient used by the handler to make the /api/cache/flush API call.
    async callOrThrow(
      endpoint: string,
      params: Record<string, string> = {}
    ): Promise<Record<string, unknown>> {
      const result = await this.call(endpoint, params);
    
      if (result.status !== "ok") {
        throw new Error(
          result.errorMessage || `API error: ${result.status}`
        );
      }
    
      return result.response || {};
    }
  • Rate limiting registration: dns_flush_cache is configured with destructiveLimits (5 requests per 60 seconds) in the RateLimiter constructor.
    for (const tool of [
      "dns_delete_zone", "dns_delete_record", "dns_flush_cache",
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 explains that the tool flushes the entire cache and requires confirm, and mentions the warning behavior without confirm. However, it does not disclose potential side effects or other behavioral details.

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 sentences, no fluff, front-loaded with the core action. Every sentence earns its place.

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?

For a simple one-param tool with no output schema, the description covers purpose and the key usage requirement. Missing return value info but not critical for this operation.

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% with a clear description for confirm. The tool description repeats the requirement but adds little extra meaning beyond what the schema already provides.

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 'Flush the entire DNS cache' with a specific verb and resource. It distinguishes from siblings like dns_flush_allowed and dns_flush_blocked by indicating this flushes the entire cache.

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

Usage Guidelines3/5

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

The description provides the requirement for confirm=true but lacks explicit guidance on when to use this tool versus alternatives like dns_flush_allowed or dns_flush_blocked.

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