opencti-mcp

search_organization

Search OpenCTI threat intelligence for organizations like companies and government bodies using a name or keyword. Retrieve matching results with configurable limits.

Instructions

Search for organizations (companies, government bodies, etc.).

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_organization"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Sep 6, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations available, the description must carry the behavioral burden. 'Search for organizations' implies a non-mutating lookup, but it does not describe match semantics, scoping, pagination, or result contents. The behavior is minimally transparent but lacks depth.

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?

The description is a single concise sentence that delivers the core purpose and examples with no wasted words. It is easy to parse, though it could carry a bit more useful context without becoming verbose.

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 two-parameter search tool with full schema coverage, the basic invocation details are covered. However, there is no output schema and no usage guidance, so an agent still lacks context about expected results and when to choose this tool over sibling searches.

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?

The input schema already documents both parameters with descriptions, defaults, and constraints, so the baseline is 3. The description adds 'organizations' context but no additional parameter semantics beyond what the schema provides.

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?

The description identifies the exact action ('Search') and resource ('organizations') with clarifying examples like 'companies, government bodies'. It does not explicitly contrast with sibling search_* tools, but the resource type is clear enough for an agent to know what the tool targets.

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 use this tool over siblings such as search_threat_actor, search_sector, or search_location. The description only states what the tool does, not under which conditions it should be selected.

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