tenable-patch-management-logs-mcp

Overview Schema Source Related Servers Discussions Admin

search_logs

Read-onlyIdempotent

Find specific entries across Tenable Patch Management log files by text or regex, filtering by time, device, role, or severity, with context and de-duplicated multiline results.

Instructions

Search every log, including multi-line messages and stack traces.

Matches are whole entries (not single lines), de-duplicated across logs that repeat the same event, sorted by time, and redacted.

Args: pattern: Text to find (literal unless regex=true), e.g. a KB number, patch ID, client ID, content ID ("Policy_104117") or error text. regex: Treat pattern as a regular expression. case_sensitive: Default false. since: Window start (ISO or relative like 24h); default all history. until: Window end. source: Source name; omit for all sources. device: Only this device. role: "server", "client" or "setup". files: Log names or globs to search. component: Exact component name, e.g. "TenableClient". min_severity: Only entries at or above INFO/WARN/ERROR. context: Entries of context before and after each match from the same file (0-5). limit: Matches to return (1-200). offset: Skip this many matches (paging; see next_offset). order: "newest" (default) or "oldest" first.

Returns: total_matches, matches (with file, line, component, thread, codes) and paging.

Input Schema

TableJSON Schema

Name	Required	Default
`role`	No
`files`	No
`limit`	No
`order`	No	newest
`regex`	No
`since`	No
`until`	No
`device`	No
`offset`	No
`source`	No
`context`	No
`pattern`	Yes
`component`	No
`min_severity`	No
`case_sensitive`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 23, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already mark the operation as read-only, idempotent, and non-destructive. The description adds meaningful behavior beyond that: matches are whole entries, de-duplicated across logs, sorted by time, and redacted, with paging behavior disclosed. There is no contradiction with the annotations.

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 front-loaded with a one-line purpose, followed by a compact behavioral note, a well-organized Args list, and a Returns line. Every section contributes useful information and there is no filler.

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

Completeness5/5

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

For a read-only search tool with an output schema, the description covers the use case, all filter parameters, behavioral quirks, and paging/return shape. An agent has enough context to select and invoke the tool correctly without additional inference.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full parameter-documentation burden. It documents every parameter with defaults, constraints, and examples, including regex, since, source, role, files, component, min_severity, context, limit, offset, and order.

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 opens with 'Search every log', a specific verb plus resource, and adds 'including multi-line messages and stack traces' to define the scope precisely. It is clearly distinguishable from sibling analysis tools like summarize_errors or diagnose even without naming them.

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 description makes the intended use clear: search raw log entries by pattern over all logs, with rich filtering options. It does not explicitly mention alternatives or exclusion conditions, but the search semantics and filter list provide strong contextual guidance.

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

Deploy Server