Planning System MCP Server

search

Search across plans, nodes, and content to locate entities by title or text fragment.

Instructions

Text search across plans, nodes, and content. Use for finding entities by title or fragment.

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

Input Schema

Name	Required	Default
`query`	Yes
`scope`	No	global
`scope_id`	No
`filters`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.8.1Apr 29, 2026
- removedInput schema / properties / filters / description
```
Removed value: -"Optional filters"
```
- removedInput schema / properties / filters / properties / limit / description
```
Removed value: -"Maximum number of results"
```
- removedInput schema / properties / filters / properties / status / description
```
Removed value: -"Filter by status"
```
- removedInput schema / properties / filters / properties / status / enum
```
Removed value: -[
-  "draft",
-  "active",
-  "completed",
-  "archived",
-  "not_started",
-  "in_progress",
-  "blocked"
-]
```
- removedInput schema / properties / filters / properties / type / description
```
Removed value: -"Filter by type"
```
- removedInput schema / properties / filters / properties / type / enum
```
Removed value: -[
-  "plan",
-  "node",
-  "phase",
-  "task",
-  "milestone",
-  "artifact",
-  "log"
-]
```
- removedInput schema / properties / query / description
```
Removed value: -"Search query"
```
- removedInput schema / properties / scope / description
```
Removed value: -"Search scope"
```
- removedInput schema / properties / scope_id / description
```
Removed value: -"Plan ID (if scope is 'plan') or Node ID (if scope is 'node')"
```
First observedDec 29, 2025

TDQS

B3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It fails to disclose behavioral traits such as whether the operation is read-only, performance implications, authorization requirements, or rate limits. The description simply says 'text search' without detailing 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?

The description is exceptionally concise with two short sentences. Every word is purposeful with no redundancy or filler. The key information is front-loaded.

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?

For a tool with 4 parameters including a nested object and no output schema, the description is too brief. It omits details about scope, scope_id, filters, and return values. The description does not sufficiently inform an agent about how to use the parameters or what to expect from the output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description should compensate but only provides minimal meaning for the 'query' parameter. It does not explain the 'scope', 'scope_id', or 'filters' parameters, leaving their semantics unclear beyond what the schema structure offers.

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 clearly states the tool performs text search across plans, nodes, and content, specifying the verb 'search' and the resource. It also indicates usage for finding entities by title or fragment. However, it does not explicitly differentiate from sibling tools like recall_knowledge, which might also retrieve entities.

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?

The description provides a usage hint ('Use for finding entities by title or fragment') but lacks explicit guidance on when not to use this tool or alternatives. It does not address scenarios where other tools might be more appropriate.

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