Skip to main content
Glama
DynamicEndpoints

Palo Alto Device Server

run_operational_mode_command

Execute operational commands on Palo Alto firewalls to retrieve system status, monitor network traffic, and troubleshoot connectivity issues through the device management server.

Instructions

Run an operational mode command on the Palo Alto firewall

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYesCommand to run

Implementation Reference

  • Handler implementation for the 'run_operational_mode_command' tool. Extracts the command from arguments, makes a POST request to `${API_BASE_URL}/Device/Op` with the command, and returns the JSON response or throws an error.
    case 'run_operational_mode_command': {
        const { command } = request.params.arguments as { command: string };
        try {
            const response = await axios.post(
                `${API_BASE_URL}/Device/Op`,
                { command },
                {
                    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:74-87 (registration)
    Registration of the 'run_operational_mode_command' tool in the listTools response, including name, description, and input schema.
    {
        name: 'run_operational_mode_command',
        description: 'Run an operational mode command on the Palo Alto firewall',
        inputSchema: {
            type: 'object',
            properties: {
                command: {
                    type: 'string',
                    description: 'Command to run'
                }
            },
            required: ['command']
        },
    }
  • Input schema definition for the 'run_operational_mode_command' tool, specifying the 'command' parameter.
    inputSchema: {
        type: 'object',
        properties: {
            command: {
                type: 'string',
                description: 'Command to run'
            }
        },
        required: ['command']
    },
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. While 'run' implies execution, it doesn't describe what operational mode commands are, whether this requires specific permissions, if commands are destructive, what happens on execution failure, or any rate limits. This leaves significant behavioral gaps for a command execution tool.

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. It's appropriately sized for a single-parameter tool and front-loads the essential information without unnecessary elaboration.

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 command execution tool with no annotations and no output schema, the description is incomplete. It doesn't explain what operational mode commands are, what types of commands are supported, what the response format looks like, or any error conditions. Given the complexity of firewall operations, this leaves significant gaps.

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?

The input schema has 100% description coverage with the 'command' parameter well-documented. The description adds no additional parameter semantics beyond what the schema provides (it doesn't explain command syntax, examples, or constraints). Baseline 3 is appropriate when schema does the heavy lifting.

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 ('run') and target resource ('operational mode command on the Palo Alto firewall'), providing specific verb+resource pairing. However, it doesn't distinguish this tool from its siblings (like get_system_info or upgrade_firewall) in terms of scope or use case differentiation.

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, when this tool is appropriate versus other sibling tools, or any exclusions. The agent must infer usage context from the tool name alone.

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