Symantec ZTNA AIops

ztna_shared_objects

Read-only

List shared policy objects with pagination, result limits, and text filtering to support ZTNA policy review and administration.

Instructions

[READ] List shared policy objects.

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_shared_objects"
  }
}

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.4/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, and '[READ]' merely restates that. Nothing is said about pagination behavior, result ordering, or what the filter_text matching scope is, which is the behavioral detail an agent actually needs here.

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

Conciseness3/5

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

Extremely short and front-loaded, with no wasted words. However, the brevity reflects under-specification rather than efficiency, as it omits information the caller needs.

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?

With three undocumented parameters, no output schema, and no explanation of paging or filtering, the definition leaves too much unknown for an agent to invoke it confidently. Only the read-only nature is conveyed, and that comes from annotations.

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?

All three parameters (page, limit, filter_text) have 0% schema description coverage, and the description adds no meaning for any of them. 'List' only loosely hints at paging without specifying defaults or which fields filter_text searches.

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

Purpose3/5

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

States a verb ('List') and a resource ('shared policy objects'), so the basic purpose is clear. It does not distinguish the collection from the singular sibling ztna_shared_object, though the plural naming carries that implicit contrast.

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 indication of when to use this list endpoint versus the singular ztna_shared_object, or versus policy-related siblings. The '[READ]' tag only signals read-only intent, not usage context.

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