Symantec ZTNA AIops

ztna_audit_logs

Read-only

Search tenant audit logs within a specified time range and paginate results using an explicit cursor for bounded, repeatable audits.

Instructions

[READ] Search bounded tenant audit logs with an explicit cursor.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "start_ms": "<start_ms>",
      "end_ms": "<end_ms>"
    },
    "name": "ztna_audit_logs"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`end_ms`	Yes
`start_ms`	Yes
`cursor_id`	No
`free_text`	No
`cursor_time`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

C2.8/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, so the "[READ]" prefix adds nothing beyond structured data. The description omits the genuinely non-obvious behavior: what "bounded" means (window size limits, max range), result ordering, and how cursor_time and cursor_id must be combined for pagination. With no annotations covering those traits, this is a real gap.

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?

One short, front-loaded sentence with the read-only marker first and no filler. It is compact, though the brevity is partly under-specification rather than discipline.

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 6-parameter search tool with 0% schema coverage, no output schema, and only a readOnlyHint, the description should explain the time-window bounds and cursor contract. The complexity is moderate, so leaving those unexplained leaves the agent to guess at call-correctness details.

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%, so the description must carry parameter meaning and it does not. "Bounded" loosely gestures at start_ms/end_ms, and "cursor" gestures at cursor_id/cursor_time, but limit, free_text, and the required pairing of the two cursor fields are never explained. An agent cannot determine units, defaults, or tie-break semantics from either source.

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?

"Search bounded tenant audit logs" gives a specific verb (search) and resource (tenant audit logs), which is enough to distinguish it from the sibling set, none of which touch audit logs. The qualifiers "bounded" and "explicit cursor" are left undefined, so the purpose is recognizable but not fully precise.

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?

There is no statement of when to use this versus anything else, no prerequisite or permission context, and no explanation of when a cursor should be supplied versus a fresh search run. The phrase "explicit cursor" hints at pagination but never says so.

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