Skip to main content
Glama
Sign In
tenable-mcp

tenable-mcp

by nguyenthdat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

tenable_download_scan_export

Read-only

Export a Tenable scan to a specified file path and format, with options for chapters and password protection.

Instructions

Export a scan and save it to a specified file path.

Use this when you need to control where the exported file is saved, rather than using a temporary location.

Example: Input: { "scan_id": 123, "output_path": "/home/user/weekly_scan.csv", "format": "csv" } Output: {"file_path": "/home/user/weekly_scan.csv", "status": "completed"}

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": {
      "scan_id": "<scan_id>",
      "output_path": "<output_path>"
    },
    "name": "tenable_download_scan_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNonessus
scan_idYes
chaptersNo
passwordNo
output_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Description relies on readOnlyHint annotation for safety profile, adding no extra behavioral context beyond the export action. No details on file overwrite, permissions, or failure modes.

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?

Very concise: three sentences plus a clear example. No redundant information; front-loaded with core purpose and when-to-use.

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

Completeness4/5

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

Provides enough context for typical use with example output, but lacks explanation of optional parameters (chapters, password) and detailed behavior on failure. Good for a download tool with annotations.

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

Parameters3/5

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

Schema has 0% description coverage; description explains scan_id, output_path, and format via example, but does not cover chapters or password parameters. Adds some meaning beyond schema but incomplete.

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?

Clearly states the tool exports a scan and saves to a specified file path. Distinguishes from sibling 'tenable_export_scan' by focusing on user-controlled output location vs temporary.

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

Usage Guidelines5/5

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

Explicitly says 'Use this when you need to control where the exported file is saved, rather than using a temporary location,' providing clear guidance on when to use this tool over alternatives.

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