lilbee

Overview Schema Source Related Servers Discussions Admin

search

Locate information across indexed documents, code, and crawled pages, returning cited chunks. Filter results by scope.

Instructions

Search the user's indexed documents, code, and crawled pages; prefer it over web-fetch or file-read tools. Returns chunks with citations. scope: "both" (default) / "raw" / "wiki". No wiki layer here: use scope "raw" or "both".

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	Description	Default
`query`	Yes
`scope`	No
`top_k`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv1.0.2Jul 22, 2026
- removedInput schema / properties / query / title
```
Removed value: -"Query"
```
- removedInput schema / properties / scope / default
```
Removed value: -"both"
```
- removedInput schema / properties / scope / title
```
Removed value: -"Scope"
```
- removedInput schema / properties / top_k / anyOf
```
Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / top_k / default
```
Removed value: -null
```
- removedInput schema / properties / top_k / title
```
Removed value: -"Top K"
```
- addedInput schema / properties / top_k / type
```
Added value: +"integer"
```
- removedInput schema / title
```
Removed value: -"searchArguments"
```
First observedv1.0.0Jun 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Describes return format (chunks with citations) and scope semantics. No annotations provided, so description carries full burden; lacks details on top_k range or rate limits, but adds useful context beyond schema.

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?

Two sentences plus a scope note; no fluff. Front-loaded purpose and guidelines.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, usage, scope, and output format. Lacks top_k default/range and any mention of permissions, but given output schema exists, it's sufficiently complete.

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

Parameters4/5

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

Schema has 0% coverage, so description compensates by explaining scope values and default. Query is assumed, top_k is not explained but is self-explanatory. Still, partial coverage justifies 4.

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 tool searches indexed documents, code, and crawled pages, distinguishing it from web-fetch or file-read tools. It specifies the verb and resources, with a clear preference note.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly recommends this tool over web-fetch or file-read, and clarifies scope usage with default values and wiki limitation. Missing when-not-to-use conditions.

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