Skip to main content
Glama

scan_vulnerabilities

Triggers vulnerability scans for specified configuration items or CI groups, with full, quick, or compliance scan types and optional background job handling.

Instructions

Trigger a vulnerability scan for specified CIs or groups. [Write]

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

Input Schema

NameRequiredDescriptionDefault
asyncNoRun as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.
groupNoCI group to scan (alternative to ci_sys_ids)
scan_typeNoScan type: full, quick, compliance (default full)
ci_sys_idsNoCI sys_ids to scan

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / async
      Added value: +{
      +  "description": "Run as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.",
      +  "type": "boolean"
      +}
  2. First observedv1.0.2

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, and the '[Write]' tag merely restates that. The description adds no operational context such as whether scans can be re-run safely, what permissions are required, or what is returned after triggering. The useful async/job behavior lives in the schema, not the description.

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?

The description is a single front-loaded sentence with no filler. The '[Write]' marker is redundant with the annotations, keeping it just short of a 5.

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?

For a write trigger with four optional parameters and no output schema, the description is minimally adequate. It omits what triggering produces, how background jobs surface, and how this differs from the other scan-related siblings, leaving meaningful gaps for an agent selecting among them.

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 description coverage is 100%, so the schema already documents async, group, scan_type, and ci_sys_ids thoroughly. The description only reinforces the CI-or-group targeting at a high level, so the baseline of 3 is appropriate.

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 states a specific verb and resource: 'Trigger a vulnerability scan for specified CIs or groups.' That is enough to distinguish it from read-oriented siblings like list_vulnerabilities, though it never explicitly contrasts itself with the similar-sounding run_discovery_scan.

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?

There is no when-to-use guidance, no prerequisites, and no routing to alternatives. The agent is left to infer how this differs from run_discovery_scan or when to use 'group' versus 'ci_sys_ids' from the schema alone.

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