Skip to main content
Glama
DynamicEndpoints

Palo Alto Device Server

upgrade_ha_firewalls_from_panorama

Upgrade PAN-OS on multiple high-availability firewalls centrally through Panorama to maintain security and performance.

Instructions

Upgrade PAN-OS on Multiple HA Firewalls through Panorama

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for the 'upgrade_ha_firewalls_from_panorama' tool. It sends a POST request to the Panorama/UpgradeHA API endpoint using axios and returns the JSON response, with error handling.
    case 'upgrade_ha_firewalls_from_panorama': {
        try {
            const response = await axios.post(
                `${API_BASE_URL}/Panorama/UpgradeHA`,
                {},
                {
                    headers: {
                        'X-PAN-KEY': API_KEY,
                        'Accept': 'application/json'
                    }
                }
            );
    
            return {
                content: [
                    {
                        type: 'text',
                        text: JSON.stringify(response.data, null, 2),
                    },
                ],
            };
        } catch (error) {
            const axiosError = error as AxiosError;
            throw new McpError(
                ErrorCode.InternalError,
                `Palo Alto API error: ${axiosError.message}`
            );
        }
    }
  • src/index.ts:50-57 (registration)
    Registration of the 'upgrade_ha_firewalls_from_panorama' tool in the list of tools returned by ListToolsRequestSchema, including name, description, and empty input schema.
    {
        name: 'upgrade_ha_firewalls_from_panorama',
        description: 'Upgrade PAN-OS on Multiple HA Firewalls through Panorama',
        inputSchema: {
            type: 'object',
            properties: {},
        },
    },
  • Input schema for the tool, which is an empty object (no parameters required).
    inputSchema: {
        type: 'object',
        properties: {},
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions upgrading PAN-OS, which implies a potentially destructive or high-impact operation, but fails to detail critical aspects such as required permissions, downtime implications, rollback options, or any rate limits. This leaves significant gaps for safe and effective use.

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, clear sentence with zero wasted words. It front-loads the key action and target, making it highly efficient and easy to parse at a glance.

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 upgrading HA firewalls (a high-risk operation), the lack of annotations, no output schema, and no parameter details, the description is insufficient. It doesn't cover behavioral traits, error handling, or expected outcomes, leaving the agent with inadequate context for safe invocation.

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 input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description doesn't add parameter details, but since there are no parameters, this is acceptable. A baseline score of 4 reflects that the description doesn't need to compensate for missing parameter information.

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 ('Upgrade PAN-OS') and target resources ('Multiple HA Firewalls through Panorama'), providing a specific verb+resource combination. However, it doesn't explicitly distinguish this tool from its sibling 'upgrade_firewall', which appears to be a similar operation but might differ in scope or method.

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?

No guidance is provided on when to use this tool versus alternatives like 'upgrade_firewall' or other siblings. The description implies it's for upgrading HA firewalls via Panorama, but it doesn't specify prerequisites, constraints, or scenarios where this tool is preferred over others.

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/DynamicEndpoints/paloalto-device-server'

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