opencti-mcp

search_grouping

Find analysis containers that group related entities by searching by name or keyword.

Instructions

Search for groupings (analysis containers that group related entities).

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": {
      "query": "<query>"
    },
    "name": "search_grouping"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max results (default: 10, max: 50)
`query`	Yes	Grouping name or keyword

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Sep 6, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits itself, but it only restates 'search' and defines the resource. It doesn't mention read-only behavior, pagination, result contents, rate limits, or any side effects.

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?

Single sentence with no filler; the resource definition is front-loaded and the entire description is easy to parse. Every word earns its place.

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?

For a simple 2-parameter search tool with a fully documented schema, this is minimally adequate for invocation. However, with no output schema and no annotations, it leaves return-value expectations and safe-use context to inference, and it doesn't help route from the large sibling set.

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 baseline is 3. The description adds useful context about the meaning of groupings, but it adds no parameter-specific details beyond what the input schema already provides for query and limit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific action ('Search for groupings') and a resource, with a parenthetical defining what a grouping is ('analysis containers that group related entities'). This makes the tool's target clear, though it does not explicitly distinguish it from the many sibling search_* tools.

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 guidance is provided about when to choose this tool over the 28 sibling search tools. The description only says what it searches for; it never states when to use it, when not to, or which alternative to pick.

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