Skip to main content
Glama
amittell

firewalla-mcp-server

delete_target_list

Remove a target list from Firewalla MSP firewall to manage network security rules and reduce attack surface by eliminating outdated or unnecessary access controls.

Instructions

Delete a target list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTarget list ID to delete (required)

Implementation Reference

  • The DeleteTargetListHandler class implements the core logic for the 'delete_target_list' tool. It validates the required 'id' parameter, calls firewalla.deleteTargetList(id), handles errors and timeouts, and returns a unified response.
    export class DeleteTargetListHandler extends BaseToolHandler {
      name = 'delete_target_list';
      description = 'Delete a target list from Firewalla';
      category = 'rule' as const;
    
      constructor() {
        super({
          enableGeoEnrichment: false,
          enableFieldNormalization: true,
          additionalMeta: {
            data_source: 'target_lists',
            entity_type: 'target_list_deletion',
            supports_geographic_enrichment: false,
            supports_field_normalization: true,
            standardization_version: '2.0.0',
          },
        });
      }
    
      async execute(
        args: ToolArgs,
        firewalla: FirewallaClient
      ): Promise<ToolResponse> {
        try {
          const idValidation = ParameterValidator.validateRequiredString(
            args?.id,
            'id'
          );
    
          if (!idValidation.isValid) {
            return createErrorResponse(
              this.name,
              'Parameter validation failed',
              ErrorType.VALIDATION_ERROR,
              undefined,
              idValidation.errors
            );
          }
    
          const id = idValidation.sanitizedValue as string;
    
          const response = await withToolTimeout(
            async () => firewalla.deleteTargetList(id),
            this.name
          );
    
          return this.createUnifiedResponse(response);
        } catch (error: unknown) {
          if (error instanceof TimeoutError) {
            return createTimeoutErrorResponse(this.name, error.duration, 10000);
          }
    
          const errorMessage =
            error instanceof Error ? error.message : 'Unknown error occurred';
          return createErrorResponse(
            this.name,
            `Failed to delete target list: ${errorMessage}`,
            ErrorType.API_ERROR,
            { id: args?.id }
          );
        }
      }
    }
  • MCP tool schema definition for 'delete_target_list' including input schema requiring 'id' string parameter.
      name: 'delete_target_list',
      description: 'Delete a target list',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'Target list ID to delete (required)',
          },
        },
        required: ['id'],
      },
    },
  • Registration of DeleteTargetListHandler instance in the ToolRegistry during auto-registration of rule tools.
    this.register(new DeleteTargetListHandler());
  • Import statement for DeleteTargetListHandler from rules handlers module.
      DeleteTargetListHandler,
      GetNetworkRulesSummaryHandler,
    } from './handlers/rules.js';
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. While 'Delete' implies a destructive mutation, the description doesn't specify whether this action is reversible, requires specific permissions, has side effects (e.g., affecting related data), or provides confirmation feedback. This is a significant gap for a mutation tool with zero annotation coverage.

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, efficient sentence with zero waste—'Delete a target list'—making it front-loaded and appropriately sized for its purpose. Every word earns its place without redundancy.

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

Completeness2/5

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

Given this is a destructive mutation tool with no annotations and no output schema, the description is incomplete. It lacks crucial details like behavioral traits (e.g., irreversibility, permissions), usage context, and what happens post-deletion. For a tool with this complexity and minimal structured data, more information is needed.

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%, with the single parameter 'id' documented as 'Target list ID to delete (required)'. The description adds no additional meaning beyond this, such as format examples or constraints. Baseline 3 is appropriate when the schema handles parameter documentation adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Delete') and the resource ('a target list'), providing a specific verb+resource combination. However, it doesn't differentiate this tool from sibling tools like 'update_target_list' or 'get_target_lists' beyond the basic action, missing explicit sibling distinction.

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 no mentions of prerequisites (e.g., needing an existing target list), exclusions, or comparisons to siblings like 'update_target_list' or 'get_target_lists', leaving usage context unclear.

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/amittell/firewalla-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server