Skip to main content
Glama
Bitdefender GravityZone MCP Server

Bitdefender GravityZone MCP Server

by WYRE-AI

bitdefender_list_incidents

Lists EDR/XDR incidents with IDs, type, status, priority, action and timestamps, filterable by endpoint, so you can review endpoint or organization incidents and retrieve full details.

Instructions

List EDR/XDR incidents (endpoint and organization incidents) - incidentId, incidentNumber, type, company, status, main action (reported/blocked/partially_blocked), priority and timestamps. Incident IDs from this response are required by bitdefender_get_incident. Scope to one machine with filters.endpointId (from bitdefender_list_endpoints). Needs a GravityZone license that includes incidents and an API key with the Incidents API enabled. Read-only - status, priority, notes and assignment are never changed. Returns a paginated envelope: page/pagesCount/perPage/total/items.

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

Input Schema

NameRequiredDescriptionDefault
pageNoResults page number (1-based). Defaults to 1.
sortByNoSort field, newest first. Defaults to lastUpdated.
filtersNoOptional filters; all selected filters must match. Each date pair (startDate+endDate, processedStartDate+processedEndDate, changeStartDate+changeEndDate) must be sent together, ISO 8601, start before end.
perPageNoItems per page (10-100). Defaults to 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it declares read-only behavior and specifically states that status, priority, notes, and assignment are never changed, ruling out mutation concerns. It adds license and API-key prerequisites and describes the paginated return envelope (page/pagesCount/perPage/total/items), all of which are behavioral facts not present in the schema or annotations.

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 dense but front-loaded: purpose, key returned fields, downstream dependency, scoping filter, prerequisites, read-only guarantee, and return shape appear in that order with no filler. Every sentence carries actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a nested filter object, no annotations, and no output schema, the description covers the missing pieces: it explains the return envelope keys, documents the read-only guarantee, and states license/API-key prerequisites. An agent has everything needed to decide to call it and to understand the shape of the response.

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 every parameter, including filter enum values, date-pair requirements, and defaults. The description only reinforces endpointId's origin ('from bitdefender_list_endpoints'), which the schema already notes, so it adds little beyond the structured field documentation. Baseline 3 is appropriate.

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 opens with a specific verb and resource ('List EDR/XDR incidents') and immediately disambiguates the two incident classes (endpoint and organization incidents). It names the fields returned and explains how the result feeds bitdefender_get_incident, so the agent can distinguish it from the sibling detail tool without opening either schema.

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

Usage Guidelines4/5

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

It states clear routing guidance: incident IDs from this response are required by bitdefender_get_incident, and a single machine can be targeted via filters.endpointId sourced from bitdefender_list_endpoints. It also lists prerequisites (GravityZone license and an API key with the Incidents API enabled). It stops short of an explicit 'when not to use' exclusion, which keeps it from a 5.

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