Skip to main content
Glama
packetracer

Palo Alto Networks MCP Server Suite

by packetracer

multi_move_clone_configuration

Move or clone multiple firewall configurations to new locations in Palo Alto Networks environments to streamline configuration management.

Instructions

Multi-Move or Multi-Clone the configuration of the Palo Alto firewall

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
config_pathsYesPaths to the configurations to move or clone
new_locationYesNew location for the configurations
actionYesAction to perform

Implementation Reference

  • Handler for the 'multi_move_clone_configuration' tool. Extracts arguments (config_paths, new_location, action), determines the API endpoint ('MultiMove' or 'MultiClone'), performs a POST request to the Palo Alto firewall's Configuration endpoint, and returns the response data as text content.
    case 'multi_move_clone_configuration': {
        const { config_paths, new_location, action } = request.params.arguments as { 
            config_paths: string[], 
            new_location: string, 
            action: 'move' | 'clone' 
        };
    
        const endpoint = action === 'move' ? 'MultiMove' : 'MultiClone';
        const response = await this.axiosInstance.post(
            `/Configuration/${endpoint}`,
            { config_paths, new_location }
        );
    
        return {
            content: [
                {
                    type: 'text',
                    text: JSON.stringify(response.data, null, 2),
                },
            ],
        };
    }
  • Input schema defining the parameters for the 'multi_move_clone_configuration' tool: config_paths (array of strings), new_location (string), and action (string enum: 'move' or 'clone').
    inputSchema: {
        type: 'object',
        properties: {
            config_paths: {
                type: 'array',
                items: {
                    type: 'string'
                },
                description: 'Paths to the configurations to move or clone'
            },
            new_location: {
                type: 'string',
                description: 'New location for the configurations'
            },
            action: {
                type: 'string',
                enum: ['move', 'clone'],
                description: 'Action to perform'
            }
        },
        required: ['config_paths', 'new_location', 'action']
    }
  • src/index.ts:173-198 (registration)
    Registration of the 'multi_move_clone_configuration' tool in the MCP server's list of tools, specifying its name, description, and input schema.
    {
        name: 'multi_move_clone_configuration',
        description: 'Multi-Move or Multi-Clone the configuration of the Palo Alto firewall',
        inputSchema: {
            type: 'object',
            properties: {
                config_paths: {
                    type: 'array',
                    items: {
                        type: 'string'
                    },
                    description: 'Paths to the configurations to move or clone'
                },
                new_location: {
                    type: 'string',
                    description: 'New location for the configurations'
                },
                action: {
                    type: 'string',
                    enum: ['move', 'clone'],
                    description: 'Action to perform'
                }
            },
            required: ['config_paths', 'new_location', 'action']
        }
    }
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 mentions 'Multi-Move or Multi-Clone' but doesn't clarify critical aspects like whether this is a destructive operation (e.g., if 'move' deletes the original), potential side effects, error handling, or performance implications. This leaves significant gaps in understanding the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the key action and resource, making it easy to grasp quickly. However, it could be slightly more structured by explicitly separating the 'move' and 'clone' options for clarity.

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 the complexity of a firewall configuration tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits, error handling, and what the tool returns (e.g., success status or error messages). For a mutation tool like this, more context is needed to ensure safe and effective use.

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%, so the schema already documents all parameters ('config_paths', 'new_location', 'action') with clear descriptions. The description adds no additional meaning beyond what the schema provides, such as explaining path formats or the implications of 'move' vs. 'clone'. Thus, it meets the baseline but doesn't enhance parameter understanding.

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 ('Multi-Move or Multi-Clone') and the resource ('configuration of the Palo Alto firewall'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'view_config_node_values' or 'list_resources', which might also involve configuration operations, leaving some ambiguity about when this specific tool should be used versus others.

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. It doesn't mention prerequisites, such as needing specific permissions or existing configurations, or when to choose 'move' vs. 'clone' actions. Without this context, users might struggle to apply it correctly in different scenarios.

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/packetracer/mcpserver'

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