Skip to main content
Glama
Sign In
tenable-mcp

tenable-mcp

by nguyenthdat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

tenable_list_scans

Read-only

List all configured scans, with optional filters by folder or name. Returns scan details including identifiers and status.

Instructions

List configured scans.

Returns a list of all scans (or filtered by folder/name).

Example: Input: {"limit": 20} Output: {"scans": [...], "total": 5}

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": "tenable_list_scans"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
limitNo
folder_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations confirm read-only. Description adds an example output structure and mentions filtering. No contradictions. Details beyond annotations are limited but sufficient for a simple list operation.

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?

Two concise sentences plus an example. Front-loaded purpose, no wasted words. The example is helpful.

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?

Given 3 optional parameters and no output schema, the description is adequate but lacks details on output structure beyond the example. Does not address pagination or limits behavior.

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 coverage is 0%. Description explains name and folder_id filters but not the limit parameter. The example shows limit usage but without explanation. Partial compensation.

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 lists configured scans and can filter by folder or name. It distinguishes from siblings like tenable_get_scan which retrieves a single scan.

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

Usage Guidelines3/5

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

The description implies usage for listing scans with optional filters but does not explicitly compare to alternatives or state when not to use it.

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