Skip to main content
Glama

get_network_services

Read-onlyIdempotent

Retrieve read-only DNS, DHCP, NTP, syslog, SNMP, TACACS+, and RADIUS configuration and status from Prisma SD-WAN.

Instructions

Inspect DNS, DHCP, NTP, syslog, SNMP, TACACS+, and RADIUS read-only state.

Site/element names are resolved to controller IDs. ntp_status accepts object_id as an NTP configuration ID; if omitted and exactly one NTP configuration exists on the element, that ID is used automatically.

Args: operation: Which read to run. No params required: dns_profiles, dns_roles, syslog_profiles, tacacs_profiles. Requires site + element: dns_services, syslog_servers, snmp_agents, snmp_traps, tacacs_servers. Requires site only: dhcp_servers. Requires element only: ntp, radius, ntp_status (ntp_status also takes optional object_id). site: Site name or controller ID. Required by some operations (see operation); resolved the same way as find_site — ambiguous or unknown names return an error instead of guessing. element: Element name or controller ID. Required by some operations (see operation); resolved the same way as find_element. object_id: Only used by ntp_status, as an NTP configuration ID. Omit it if the element has exactly one NTP configuration — it is picked automatically. If it has more than one, this call fails with the candidate IDs listed; pass one of them here. cursor: Opaque pagination token copied from a previous response's next_cursor. Omit on the first call. limit: Max items to return in this page. Omit to use the server default page size (50; max 200).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteNoSite name or controller ID. Required by some operations (see `operation`); resolved the same way as `find_site` — ambiguous or unknown names return an error instead of guessing.
limitNoMax items to return in this page. Omit to use the server default page size (50; max 200).
cursorNoOpaque pagination token copied from a previous response's `next_cursor`. Omit on the first call.
elementNoElement name or controller ID. Required by some operations (see `operation`); resolved the same way as `find_element`.
object_idNoOnly used by ``ntp_status``, as an NTP configuration ID. Omit it if the element has exactly one NTP configuration — it is picked automatically. If it has more than one, this call fails with the candidate IDs listed; pass one of them here.
operationYesWhich read to run. No params required: ``dns_profiles``, ``dns_roles``, ``syslog_profiles``, ``tacacs_profiles``. Requires ``site`` + ``element``: ``dns_services``, ``syslog_servers``, ``snmp_agents``, ``snmp_traps``, ``tacacs_servers``. Requires ``site`` only: ``dhcp_servers``. Requires ``element`` only: ``ntp``, ``radius``, ``ntp_status`` (``ntp_status`` also takes optional ``object_id``).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, but the description adds valuable behavioral context: site/element names resolve to controller IDs, ambiguous names return an error instead of guessing, ntp_status auto-selects an NTP config if exactly one exists and lists candidate IDs if more, and pagination uses an opaque cursor with a page size default of 50 and max of 200.

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 opens with a one-line summary, then uses an 'Args' list to detail each parameter. Although it is long (~250 words), every sentence carries operational necessity: operation groupings, resolution behavior, edge-case handling, and pagination. No waste.

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

Completeness5/5

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

Given the complexity (6 parameters, 13 operation enums, variable required-parameter combinations), the description is exhaustive: it covers resolution semantics, per-operation requirements, ntp_status fallback and failure behavior, pagination, and page size limits. An output schema exists, so return-value details are not needed.

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 coverage is 100% — every parameter has a description, including the operation enum values grouped by required inputs. The description essentially repeats the schema's parameter descriptions (e.g., site resolution, object_id behavior) without adding new semantic meaning, so it meets the baseline but does not exceed it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Inspect DNS, DHCP, NTP, syslog, SNMP, TACACS+, and RADIUS read-only state' — a specific verb ('Inspect') paired with an explicit enumerated resource set. This clearly differentiates the tool from siblings like get_routing, get_wan, and get_interfaces by naming the exact service scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear per-operation guidance: 'No params required: dns_profiles...' and lists which operations require site, element, or both. It does not explicitly mention alternatives like 'for routing use get_routing', but the tool is self-contained and the parameter requirements effectively tell the agent when to use this tool and how to select among its 13 operations.

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/iamdheerajdubey/prisma-sdwan-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server