Skip to main content
Glama
dreamiurg

Datadog MCP Server

by dreamiurg

list_vulnerabilities

List security vulnerability findings filtered by tool, type, severity, and status for targeted vulnerability management.

Instructions

List security vulnerability findings with filtering by tool, type, severity, and status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_tokenNoPagination token from previous response links.next
page_numberNoPage number (>= 1)
filter_typeNoVulnerability type (e.g. SqlInjection, Xss, CommandInjection, ComponentWithKnownVulnerability)
filter_toolNoDetection tool: SAST, SCA, IAST, or Infra
filter_statusNoStatus: Open, Muted, Remediated, InProgress, or AutoClosed
filter_cvss_base_severityNoBase severity: Unknown, None, Low, Medium, High, or Critical
filter_cvss_datadog_severityNoDatadog-adjusted severity: Unknown, None, Low, Medium, High, or Critical
filter_languageNoProgramming language filter
filter_ecosystemNoEcosystem: PyPI, Maven, NuGet, Npm, RubyGems, Go, Packagist, Deb, Rpm, Apk, etc.
filter_code_location_file_pathNoFilter by file path in source code
filter_fix_availableNoFilter by fix availability
filter_asset_nameNoAsset name (supports wildcards *)
filter_asset_typeNoAsset type: Repository, Service, Host, HostImage, or Image
filter_asset_environmentsNoFilter by asset environments
filter_asset_repository_urlNoFilter by repository URL
filter_asset_risks_in_productionNoFilter assets in production
filter_asset_risks_under_attackNoFilter assets under active attack
Behavior2/5

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

No annotations are provided, and the description only says 'with filtering'. It does not disclose pagination behavior, default limits, ordering, or whether the tool is read-only. For a 17-parameter tool, this is insufficient.

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, front-loaded sentence with no extraneous words. It efficiently conveys the verb and key dimensions.

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 17 parameters, no output schema, and no annotations, the description is too brief. It lacks explanations of pagination, default behavior, response format, and differentiation from similar tools like search-security-findings.

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 description adds no new meaning beyond summarizing four filter types. It omits mention of pagination parameters (page_token, page_number) and doesn't explain how filters combine.

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 it lists security vulnerability findings and enumerates key filter dimensions (tool, type, severity, status). This distinguishes it from sibling tools like search-security-findings or list-containers.

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?

No explicit guidance on when to use this tool versus others (e.g., search-security-findings). Implied usage is for listing vulnerabilities, but no excluding conditions or alternatives are mentioned.

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

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/dreamiurg/datadog-mcp'

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