Skip to main content
Glama
Sign In
tenable-mcp

tenable-mcp

by nguyenthdat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

tenable_was_download_report

Read-only

Retrieve a detailed Web Application Scanning report by providing the scan's UUID.

Instructions

Download a Web Application Scanning (WAS) report.

Retrieves the detailed report for a specific WAS scan.

Example: Input: {"scan_uuid": "123e4567-e89b-12d3-a456-426614174000"} Output: {"report": {...}, "scan_uuid": "..."}

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_uuid": "<scan_uuid>"
    },
    "name": "tenable_was_download_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
scan_uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so description's 'download' and 'retrieves' are consistent. Description adds example output but no additional behavioral details like format or size limits.

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?

Description is brief with two sentences and an example. No fluff, but the example could be more informative.

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?

No output schema, but example shows structure. Missing details on report format, file download semantics, error conditions, or authentication requirements beyond annotations.

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 only parameter, scan_uuid, has no description in schema (0% coverage) and the tool description does not explain its meaning or format beyond a placeholder example. Agent lacks guidance on how to obtain or format the UUID.

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 clearly states the tool downloads a WAS report, using specific verb 'download' and resource 'Web Application Scanning report'. It distinguishes from siblings like tenable_download_scan_export by specifying WAS context.

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 explicit guidance on when to use this tool versus alternatives like tenable_was_export or tenable_download_scan_export. The example implies usage but doesn't explain selection criteria.

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