Skip to main content
Glama
DynamicEndpoints

Palo Alto Device Server

upgrade_firewall

Upgrade Palo Alto firewall PAN-OS to maintain security compliance and access new features by applying the latest software version.

Instructions

Upgrade the Palo Alto firewall to the latest PAN-OS version

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'upgrade_firewall' tool: performs a POST request to /Device/Upgrade on the Palo Alto firewall API and returns the JSON response.
    case 'upgrade_firewall': {
        try {
            const response = await axios.post(
                `${API_BASE_URL}/Device/Upgrade`,
                {},
                {
                    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}`
            );
        }
    }
  • Input schema definition for 'upgrade_firewall' tool (no input parameters required).
    inputSchema: {
        type: 'object',
        properties: {},
    },
  • src/index.ts:42-49 (registration)
    Registration of the 'upgrade_firewall' tool in the ListToolsRequestHandler response.
    {
        name: 'upgrade_firewall',
        description: 'Upgrade the Palo Alto firewall to the latest PAN-OS version',
        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 full burden for behavioral disclosure. It states this is an upgrade operation which implies a potentially disruptive system change, but doesn't mention downtime implications, rollback capabilities, authentication requirements, or what happens during the upgrade process. For a zero-parameter tool that performs system upgrades, this is a significant behavioral information gap.

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 that communicates the core purpose without unnecessary words. It's appropriately sized for a zero-parameter tool and front-loads the essential information. Every word earns its place.

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?

For a system upgrade tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the upgrade entails, potential risks, expected duration, success indicators, or what happens if the upgrade fails. Given the complexity of firewall upgrades and the lack of structured behavioral information, the description should provide more operational context.

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 with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and the schema coverage is complete. No additional parameter information is needed or provided.

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') and target resource ('Palo Alto firewall'), specifying the upgrade target ('latest PAN-OS version'). It distinguishes from sibling 'upgrade_ha_firewalls_from_panorama' by focusing on single firewall upgrades rather than HA clusters from Panorama. However, it doesn't explicitly differentiate from other siblings like 'check_install_content_updates' which might involve similar systems.

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 explicit guidance on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites, timing considerations, or when to choose this over other upgrade-related tools. While the name implies a specific action, there's no contextual guidance for the agent.

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