Skip to main content
Glama
Cyreslab-AI

Nessus MCP Server

list_scan_templates

Retrieve available Nessus scan templates to configure and execute vulnerability assessments effectively using the MCP server.

Instructions

List available Nessus scan templates

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the list_scan_templates tool. It calls getScanTemplates() from the Nessus API and returns the formatted list or handles errors.
    export const listScanTemplatesToolHandler = async () => {
      try {
        const templates = await getScanTemplates();
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(templates, null, 2)
            }
          ]
        };
      } catch (error) {
        const mcpError = handleNessusApiError(error);
        return {
          content: [
            {
              type: 'text',
              text: `Error: ${mcpError.message}`
            }
          ],
          isError: true
        };
      }
    };
  • The schema definition for the list_scan_templates tool, specifying name, description, and empty input schema (no parameters required).
    export const listScanTemplatesToolSchema = {
      name: 'list_scan_templates',
      description: 'List available Nessus scan templates',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    };
  • src/index.ts:97-98 (registration)
    Registration and dispatch of the list_scan_templates handler in the main tool call switch statement.
    case 'list_scan_templates':
      return await listScanTemplatesToolHandler();
  • src/index.ts:76-76 (registration)
    Registration of the list_scan_templates schema in the listTools response.
    listScanTemplatesToolSchema,
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits. It doesn't mention if this is a read-only operation, what the output format might be, or any constraints like rate limits, leaving significant gaps in understanding how the tool behaves.

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 a single, clear sentence with no wasted words, making it highly efficient and front-loaded. It directly communicates the core purpose without unnecessary elaboration, which is ideal for a simple tool.

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?

Given the tool's simplicity (0 parameters, no annotations, no output schema), the description is minimal but incomplete. It doesn't explain what 'scan templates' entail or provide context about the return values, leaving the agent with insufficient information to fully understand the tool's role in the Nessus ecosystem.

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

Parameters4/5

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

The tool has 0 parameters, and the input schema has 100% coverage with no properties. The description doesn't need to add parameter details, so it appropriately avoids redundancy. A baseline of 4 is applied since no parameters exist, and the description doesn't mislead about inputs.

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?

The description clearly states the action ('List') and target resource ('available Nessus scan templates'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'list_scans', which might list actual scans rather than templates, so it misses full sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives like 'list_scans' or 'start_scan'. It lacks context about prerequisites, such as whether authentication is needed or if this is for planning scans, leaving the agent with no usage direction.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Cyreslab-AI/nessus-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server