Symantec ZTNA AIops

ztna_connectors

Read-only

Lists one page of ZTNA connectors with pagination and text filtering, enabling inspection of connector inventory and status.

Instructions

[READ] List one page of connectors.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ztna_connectors"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`limit`	No
`filter_text`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

C2.7/5.0

Behavior3/5

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

The readOnlyHint annotation already establishes that this is a read operation, and '[READ]' merely repeats it. The phrase 'one page' adds pagination scope, but the description does not clarify maximum page size, filter behavior, defaults, or authentication needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with little filler, though '[READ]' is redundant with the readOnlyHint annotation. Its terseness is structurally clean but contributes to the missing semantics.

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?

For a three-parameter list tool with no schema descriptions and no output schema, the description omits pagination mechanics, filter semantics, defaults, and any return-shape guidance. It identifies the resource and page scope but is not complete enough to call confidently.

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

Parameters1/5

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

The schema has three parameters with 0% description coverage, and the description does not explain page indexing, limit defaults or bounds, or what filter_text matches against. 'One page' only loosely hints at the page parameter and does not compensate for the undocumented schema.

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?

States a specific verb ('List') and resource ('connectors') and adds the scope 'one page'. The plural/list wording distinguishes it from the singular sibling ztna_connector, but the description does not explicitly differentiate among siblings.

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?

Provides no explicit when-to-use or when-not-to-use guidance and names no alternatives. The only signal is 'List one page', leaving the agent to infer that ztna_connector should be used for a single connector.

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