Skip to main content
Glama
packetracer

Palo Alto Networks MCP Server Suite

by packetracer

view_config_node_values

Retrieve configuration values from Palo Alto firewalls using XPath queries to inspect and manage security policies, network objects, and system settings.

Instructions

View configuration node values for XPath on the Palo Alto firewall

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xpathYesXPath to the configuration node

Implementation Reference

  • Handler that fetches and returns the configuration node values for the given XPath using the Palo Alto firewall API.
    case 'view_config_node_values': {
        const { xpath } = request.params.arguments as { xpath: string };
        const response = await this.axiosInstance.get('/config/xpath', {
            params: { xpath }
        });
        return {
            content: [
                {
                    type: 'text',
                    text: JSON.stringify(response.data, null, 2),
                },
            ],
        };
    }
  • src/index.ts:159-172 (registration)
    Registers the 'view_config_node_values' tool including its name, description, and input schema in the list_tools response.
    {
        name: 'view_config_node_values',
        description: 'View configuration node values for XPath on the Palo Alto firewall',
        inputSchema: {
            type: 'object',
            properties: {
                xpath: {
                    type: 'string',
                    description: 'XPath to the configuration node'
                }
            },
            required: ['xpath']
        }
    },
  • Defines the input schema for the tool, requiring a single 'xpath' string parameter.
        type: 'object',
        properties: {
            xpath: {
                type: 'string',
                description: 'XPath to the configuration node'
            }
        },
        required: ['xpath']
    }
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 states 'view,' implying a read-only operation, but doesn't specify whether this requires authentication, has rate limits, or what the output format looks like (e.g., structured data or raw text). This leaves significant gaps in understanding how the tool behaves.

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 appropriately sized for a simple tool, though it could be slightly more informative without losing conciseness.

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 interacting with a firewall configuration and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'configuration node values' entail, how results are returned, or any error conditions, leaving the agent with insufficient context for reliable 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?

The input schema has 100% description coverage, with the 'xpath' parameter documented as 'XPath to the configuration node.' The description adds no additional meaning beyond this, such as examples of valid XPath formats or common use cases. Baseline 3 is appropriate since the 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 ('view') and target ('configuration node values for XPath on the Palo Alto firewall'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_system_info' or 'list_resources', which might also retrieve information from the firewall.

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. The description lacks context about prerequisites, such as needing specific permissions or connectivity to the firewall, and doesn't mention any exclusions or preferred scenarios for usage.

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