Skip to main content
Glama
packetracer

Palo Alto Networks MCP Server Suite

by packetracer

get_system_info

Retrieve system information from Palo Alto firewalls to monitor device status and configuration details for network security management.

Instructions

Get system information from the Palo Alto firewall

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for the 'get_system_info' tool. It makes an API GET request to '/Device/VirtualSystems' using the configured axios instance and returns the response data as a text content block.
    case 'get_system_info': {
        const response = await this.axiosInstance.get('/Device/VirtualSystems');
        return {
            content: [
                {
                    type: 'text',
                    text: JSON.stringify(response.data, null, 2),
                },
            ],
        };
    }
  • src/index.ts:133-139 (registration)
    The tool registration entry in the ListTools response, including name, description, and input schema (empty object).
        name: 'get_system_info',
        description: 'Get system information from the Palo Alto firewall',
        inputSchema: {
            type: 'object',
            properties: {},
        },
    },
  • The input schema definition for the 'get_system_info' tool, which expects an empty object.
    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 states the tool retrieves information but doesn't specify what type of system information (e.g., hardware status, software versions, network stats), whether it requires authentication, rate limits, or the format of returned data. This leaves significant gaps for an agent to understand 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.

Conciseness5/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 is front-loaded with the core action and resource, making it easy to parse and understand quickly.

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 tool's complexity (simple retrieval with no parameters) but lack of annotations and output schema, the description is incomplete. It doesn't explain what information is returned, the data format, or any behavioral aspects like error handling, making it inadequate for an agent to use the tool effectively without additional 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 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter details, and it appropriately avoids mentioning any parameters, maintaining a baseline score of 4 for tools with no parameters.

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 ('Get system information') and target resource ('from the Palo Alto firewall'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'list_resources' or 'view_config_node_values', which might also retrieve information from the same system.

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 what distinguishes it from sibling tools like 'list_resources' or 'view_config_node_values', nor does it specify prerequisites, appropriate contexts, or exclusions for its use.

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