Skip to main content
Glama
solomonneas

rapid7-mcp

by solomonneas

create_investigation

Create a new InsightIDR investigation by specifying a title, priority, and status to initiate incident response.

Instructions

Create a new InsightIDR investigation with a title, priority, and status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesInvestigation title
statusNoInitial investigation statusOPEN
priorityNoInvestigation priorityMEDIUM
dispositionNoInvestigation disposition (typically set when closing)
assignee_emailNoEmail of the user to assign the investigation to
Behavior3/5

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

No annotations exist, so description must disclose behavior. It states the tool creates an investigation but omits potential side effects, permissions, or whether it returns the created object.

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?

A single sentence with no extraneous words. Front-loaded with the action and key parameters.

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?

With 5 parameters and no output schema, the description is minimal. It does not mention return values or confirmation of creation, which would be helpful for an agent.

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 each parameter. The description adds no extra meaning beyond what's in the schema (e.g., 'title, priority, and status' are already described).

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 'Create' and the resource 'InsightIDR investigation', and lists key attributes (title, priority, status). This distinguishes it from sibling tools like update_investigation and get_investigation.

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 vs alternatives. Usage is implied from the creation purpose, but no exclusion or when-not scenarios are provided.

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/solomonneas/rapid7-mcp'

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