rapid7-mcp

get_investigation_alerts

Retrieve all alerts linked to a specific investigation to correlate evidence and accelerate incident response.

Instructions

Get all alerts associated with a specific investigation

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": {
      "investigation_id": "<investigation_id>"
    },
    "name": "get_investigation_alerts"
  }
}

Input Schema

Name	Required	Description
`size`	No	Number of alerts to return (1-100)
`index`	No	Pagination index
`investigation_id`	Yes	Investigation ID or RRN

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 12, 2026

TDQS

B3/5.0

Behavior2/5

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

The description says 'Get all alerts' but the input schema includes pagination parameters (size and index), indicating it may not return all at once. This contradiction is not addressed. No annotations are provided, so the description carries full burden but fails to disclose pagination behavior or error handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but lacks structure. Important details about pagination are missing. It is not front-loaded with critical information. Every word is earned, but the sentence is too terse for a tool with pagination.

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 complexity (3 parameters, pagination, no output schema), the description is incomplete. It does not explain the pagination behavior, return format, or how to interpret 'all alerts' in the context of size and index limits.

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 input schema already documents each parameter. The description adds no additional meaning beyond the schema. Baseline score of 3 is appropriate as description does not enhance parameter understanding.

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 the verb 'get' and resource 'alerts' with the scope 'associated with a specific investigation'. It distinguishes well from siblings like get_alert (single alert) and list_alerts (all alerts potentially without investigation filter).

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?

No explicit guidance on when to use this tool versus alternatives. The description does not mention prerequisites, limitations, or when not to use it. Usage is implied by the name but not directed.

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