Skip to main content
Glama
rosschurchill

Technitium MCP Secure

dns_update_blocklists

Trigger an immediate update of all configured block lists, overriding the default 24-hour schedule.

Instructions

Force an immediate update of all configured block lists. Normally block lists update every 24 hours.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Defines the 'dns_update_blocklists' tool with its handler that calls /api/settings/forceUpdateBlockLists API endpoint to trigger an immediate block list update.
    {
      definition: {
        name: "dns_update_blocklists",
        description:
          "Force an immediate update of all configured block lists. Normally block lists update every 24 hours.",
        inputSchema: {
          type: "object",
          properties: {},
        },
      },
      readonly: false,
      handler: async () => {
        const data = await client.callOrThrow(
          "/api/settings/forceUpdateBlockLists"
        );
        return JSON.stringify(
          { success: true, message: "Block list update triggered", ...data },
          null,
          2
        );
      },
  • Input schema for dns_update_blocklists - accepts no parameters (empty object).
    inputSchema: {
      type: "object",
      properties: {},
    },
  • Tool definition registered within the settingsTools() function array in src/tools/settings.ts.
    {
      definition: {
        name: "dns_update_blocklists",
        description:
          "Force an immediate update of all configured block lists. Normally block lists update every 24 hours.",
        inputSchema: {
          type: "object",
          properties: {},
        },
      },
      readonly: false,
      handler: async () => {
        const data = await client.callOrThrow(
          "/api/settings/forceUpdateBlockLists"
        );
        return JSON.stringify(
          { success: true, message: "Block list update triggered", ...data },
          null,
          2
        );
      },
    },
  • Rate limiter registration: dns_update_blocklists is grouped with 'destructiveLimits' (5 requests per 60s window).
    for (const tool of [
      "dns_delete_zone", "dns_delete_record", "dns_flush_cache",
      "dns_flush_allowed", "dns_flush_blocked", "dns_uninstall_app",
      "dns_update_blocklists", "dns_temp_disable_blocking",
    ]) {
      this.toolLimits.set(tool, destructiveLimits);
    }
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. It says 'Force an immediate update' but does not disclose potential side effects (e.g., downtime, resetting timers) or how the update affects ongoing blocking. The description is too thin for a command that triggers a process.

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 only two sentences, no wasted words, and the key action is front-loaded. Every sentence earns its place by stating the purpose and providing context about normal update frequency.

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?

Given there are no parameters, no output schema, and the tool is simple, the description covers the essential purpose and one behavioral trait (update interval). It is mostly complete for a straightforward action, though it could mention whether the update is synchronous or if there are any side effects.

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, so according to the rubric, the baseline is 4. The description adds no parameter-specific information, which is acceptable since there are no parameters to document.

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 tool forces an immediate update of all configured block lists. It uses a specific verb and resource, and the many sibling tools (e.g., dns_block_domain, dns_flush_cache) are distinct, so no confusion.

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 implies usage is when you want an update before the normal 24-hour cycle, but it does not explicitly state when not to use it or provide alternative tools. Usage context is suggested but not fully explicit.

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