Skip to main content
Glama
DynamicEndpoints

Palo Alto Device Server

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 axios GET request to the Palo Alto API endpoint for VirtualSystems and returns the JSON response as text content.
    case 'get_system_info': {
        try {
            const response = await axios.get(
                `${API_BASE_URL}/Device/VirtualSystems`,
                {
                    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:34-41 (registration)
    Registration of the 'get_system_info' tool in the ListTools response, including its name, description, and empty input schema.
    {
        name: 'get_system_info',
        description: 'Get system information from the Palo Alto firewall',
        inputSchema: {
            type: 'object',
            properties: {},
        },
    },
  • Input schema for the 'get_system_info' tool, which requires no parameters (empty object).
    inputSchema: {
        type: 'object',
        properties: {},
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'Get system information' which implies a read-only operation, but doesn't specify what type of information is returned, whether it requires authentication, or any rate limits. This leaves significant gaps for a tool interacting with a firewall system.

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 any unnecessary words. It's appropriately sized and front-loaded, making it easy to parse.

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 and the lack of annotations and output schema, the description is insufficient. It doesn't explain what 'system information' includes, the format of the return value, or any behavioral traits like error handling. This leaves the agent with incomplete context for proper tool 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 tool has 0 parameters, and the input schema has 100% description coverage (though empty). The description doesn't need to explain parameters, so it meets the baseline for a parameterless tool. No additional parameter information is provided or required.

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') and resource ('system information from the Palo Alto firewall'), making the tool's purpose understandable. However, it doesn't distinguish this tool from its siblings (like 'run_operational_mode_command' which might also retrieve system data), so it doesn't reach the highest score.

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, context, or exclusions, leaving the agent to infer usage 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