Skip to main content
Glama
Bitdefender GravityZone MCP Server

Bitdefender GravityZone MCP Server

by WYRE-AI

bitdefender_get_incident

Retrieve complete details for a Bitdefender GravityZone incident by ID, including severity, priority, attack types, affected endpoints, alerts, MITRE tags, status history, and a Control Center link.

Instructions

Get full detail for one incident: severity score (1-100), priority, attack types (e.g. Malware, Ransomware, Password Stealer), detection name, affected computer (name, FQDN, IP, MACs), process/file nodes, alerts, MITRE tags, status history and the Control Center link. Requires an incident ID from bitdefender_list_incidents. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "bitdefender_get_incident"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIncident ID (24 hex characters), from bitdefender_list_incidents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden, and it does add value by labeling the operation 'Read-only' and disclosing the rich return payload. It does not address permissions required, whether the link expires, or error behavior for an invalid or unknown ID, which leaves meaningful gaps for a no-annotation tool.

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?

Two sentences, front-loaded with the purpose and the returned-field inventory, with the prerequisite and read-only note trailing. The field list is long but earns its place by telling the agent what payload to expect; no filler wording.

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?

No output schema exists, so the field enumeration does useful work describing the return shape, and the prerequisite is covered. However, a detail-retrieval tool with zero annotations would benefit from noting required permissions, failure modes for invalid IDs, or whether the Control Center link is time-limited.

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 100% and the schema already documents the single id parameter including the 24-hex-character format and its source. The description repeats the provenance guidance ('Requires an incident ID from bitdefender_list_incidents') but adds no format or validation detail beyond the schema, so baseline 3 applies.

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?

States a specific verb (Get) and resource (full detail for one incident) and enumerates the returned fields — severity score, priority, attack types, detection name, affected computer, process/file nodes, alerts, MITRE tags, status history, Control Center link. This clearly distinguishes it from the sibling bitdefender_list_incidents, which returns a list rather than full detail.

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?

Explicitly requires an incident ID 'from bitdefender_list_incidents,' which tells the agent the prerequisite call to make first. It does not explicitly state when-not to use it or name a narrower alternative, but the detail-vs-list distinction is conveyed through the field enumeration.

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