Skip to main content
Glama
zscaler

zscaler-mcp-server

Official
by zscaler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

zpa_get_ba_certificate

Read-only

Retrieve a ZPA Browser Access certificate by its ID to view its configuration and details.

Instructions

Get one ZPA Browser Access certificate by ID (read-only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
certificate_idYes
microtenant_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.15.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / certificate_id / title
      Added value: +"Certificate Id"
    • addedInput schema / properties / microtenant_id / title
      Added value: +"Microtenant Id"
    • addedInput schema / title
      Added value: +"zpa_get_ba_certificateArguments"
  2. Changed9 schema fields changedv0.14.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / certificate_id / description
      Removed value: -"Certificate ID for the BA certificate."
    • removedInput schema / properties / certificate_id / title
      Removed value: -"Certificate Id"
    • removedInput schema / properties / microtenant_id / description
      Removed value: -"Microtenant ID for scoping."
    • removedInput schema / properties / microtenant_id / title
      Removed value: -"Microtenant Id"
    • removedInput schema / properties / query_params
      Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Optional query parameters.",
-  "title": "Query Params"
-}
    • removedInput schema / properties / service
      Removed value: -{
-  "default": "zpa",
-  "description": "The service to use.",
-  "title": "Service",
-  "type": "string"
-}
    • removedInput schema / title
      Removed value: -"zpa_get_ba_certificateArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "additionalProperties": true,
-      "title": "Result",
-      "type": "object"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "zpa_get_ba_certificateOutput",
-  "type": "object"
-}New value: +null
  3. First observedv0.12.7

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and the description repeats 'read-only', which is consistent but adds little. The description does not disclose additional behaviors such as error handling, authentication requirements, or return format beyond what annotations provide.

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, concise sentence that is front-loaded with the key information. There is zero fluff or redundancy, making it efficient for quick comprehension.

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?

The tool is simple with no output schema or nested objects, so the description is somewhat adequate. However, it could be improved by stating what the tool returns (the certificate details) or clarifying the optional microtenant_id context. Given the low complexity, this is acceptable but not complete.

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?

Schema description coverage is 0%, and the description does not compensate by explaining the parameters. While certificate_id and microtenant_id are somewhat self-explanatory, the description offers no additional meaning or context, such as the role of microtenant_id in multi-tenant setups.

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 clearly states the action (Get), the resource (ZPA Browser Access certificate), and the scope (by ID). It effectively distinguishes from sibling list tools like zpa_list_ba_certificates, which retrieve multiple items.

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

Usage Guidelines3/5

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

The description implies usage when you have a specific certificate ID, but it does not explicitly state when to use this tool versus alternatives, nor does it provide when-not guidance or mention any prerequisites. It is clear but minimal.

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