Skip to main content
Glama
Antxine

PanOS MCP Server

by Antxine
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

userid_lookup

Read-only

Look up the user mapped to an IP address and the groups that user belongs to on a managed firewall, verifying that user/group-based rules can match that IP.

Instructions

[READ-ONLY] User-ID state on a managed firewall: which user is mapped to an IP (show user ip-user-mapping) and/or which groups a user belongs to (show user user-ids match-user). A missing mapping means user/group-based rules cannot match that IP.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipNoIP address
userNoUser name, with or without domain (e.g. 'jdoe' or 'corp\\jdoe')
deviceNoSpecific firewall (hostname or serial). Usually omit it: the firewall is chosen from device_group, or from the user's/IP's recent traffic.
firewallNoPanorama entry from firewalls.json. Optional when a single Panorama is configured.
device_groupNoDevice group name (includes what it inherits from shared and parent groups), or 'shared'. When omitted, every location is searched.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.30

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true, and the description reinforces this with '[READ-ONLY]'. It adds useful behavioral context by naming the underlying CLI commands and noting that a missing mapping means user/group-based rules cannot match that IP.

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 two sentences with no wasted words. The read-only flag and primary purpose are front-loaded, and the second sentence adds a meaningful operational implication that helps an agent understand why a missing mapping matters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the tool's purpose, the data source commands, and the real-world consequence of missing mappings, while the schema fully documents the optional parameters. It could be slightly more complete by stating what happens when no ip or user parameter is provided, but it is otherwise sufficient for a read-only lookup tool.

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?

Schema description coverage is 100%, and each parameter already has descriptive descriptions including domain examples and device-selection guidance. The description adds no additional parameter-level meaning beyond what the schema already provides.

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 names the resource ('User-ID state on a managed firewall') and the two lookups it performs: IP-to-user mapping and group membership for a user. It is specific enough to understand the tool's function, but it does not explicitly differentiate itself from the sibling tools get_userid_mappings and get_userid_groups.

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 given about when to use this tool versus the similar sibling lookup tools get_userid_mappings or get_userid_groups. The description states what the tool does but provides no conditions for selection or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools