Skip to main content
Glama
zscaler

zscaler-mcp-server

Official
by zscaler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

zpa_list_lss_status_codes

Read-only

List ZPA LSS session status codes for configuration filters. Use this read-only catalog to identify valid codes and build accurate log filters.

Instructions

List ZPA LSS session status codes used in config filters (read-only catalog).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
log_typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYesCatalog kind (e.g. log_types, log_format, status_codes).
itemsYesThe catalog payload as returned by ZPA.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.15.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / log_type / title
      Added value: +"Log Type"
    • addedInput schema / title
      Added value: +"zpa_list_lss_status_codesArguments"
  2. Changed12 schema fields changedv0.14.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / log_type / description
      Removed value: -"Optional human-readable LSS log type to filter status codes (e.g. `user_activity`). Omit to return all status codes across all log types."
    • removedInput schema / properties / log_type / title
      Removed value: -"Log Type"
    • removedInput schema / properties / service
      Removed value: -{
-  "default": "zpa",
-  "description": "The service to use.",
-  "title": "Service",
-  "type": "string"
-}
    • removedInput schema / title
      Removed value: -"zpa_list_lss_status_codesArguments"
    • addedOutput schema / additionalProperties
      Added value: +true
    • addedOutput schema / description
      Added value: +"Generic catalog wrapper — keeps the SDK payload intact under `items`.\n\nThe LSS metadata endpoints return free-form dicts/lists (log types, format\ntemplates, status codes, client types). We pass them through under a single\ncurated container rather than inventing per-catalog schemas."
    • addedOutput schema / properties / items
      Added value: +{
+  "description": "The catalog payload as returned by ZPA.",
+  "title": "Items"
+}
    • addedOutput schema / properties / kind
      Added value: +{
+  "description": "Catalog kind (e.g. log_types, log_format, status_codes).",
+  "title": "Kind",
+  "type": "string"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "additionalProperties": true,
-  "title": "Result",
-  "type": "object"
-}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "kind",
+  "items"
+]
    • changedOutput schema / title
      Previous value: -"zpa_list_lss_status_codesOutput"New value: +"Catalog"
  3. First observedv0.12.7

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description's 'read-only catalog' is redundant but harmless. It adds minimal behavioral context ('used in config filters') but doesn't disclose parameter effects or output shape, which is acceptable given the annotations cover the safety profile.

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 sentence that gets straight to the point, with the verb and resource front-loaded. No wasted words.

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

Completeness3/5

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

For a simple list tool with an output schema, the description covers purpose and read-only nature, but it omits any explanation of the log_type parameter, which is a notable gap. The tool is not fully self-explanatory without that detail.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter log_type is completely ignored by the description, and the schema has no description either (schema description coverage 0%). The description does not explain how log_type affects results, leaving a significant ambiguity for a parameter that is optional but likely meaningful for filtering.

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 uses a specific verb ('List'), identifies a distinct resource ('ZPA LSS session status codes'), and adds a qualifier ('used in config filters') that differentiates it from sibling tools like zpa_list_lss_client_types or zpa_list_lss_log_types.

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 phrase 'used in config filters' provides clear context on when to use this tool. While it doesn't explicitly name alternatives or exclusions, the resource is specific enough that agents can infer its purpose relative to sibling tools.

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