Find text across wiki pages, case-insensitive by default, with subfolder and case-sensitive options.
Simple full-text search (case-insensitive by default) across all wiki pages.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | String to search for. | |
| subdir | No | Restrict the search to a subfolder. | |
| max_results | No | Maximum number of matches returned. | |
| case_sensitive | No | If true, the search is case-sensitive. |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It usefully discloses the case-insensitive default and that the scope is all wiki pages, but omits the return format (page names vs. snippets) and any pagination/limit behavior, leaving key traits unstated.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler or redundancy. The core purpose and behavior are conveyed immediately.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a search tool with no output schema, the description should indicate what matches look like or how results are returned; it does not. It is adequate to invoke but leaves the agent guessing about return shape and result ranking.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the schema already documents query, subdir, max_results, and case_sensitive. The description adds only the case-insensitivity default, which duplicates the schema's default value, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource (full-text search across wiki pages) and the default matching behavior. It distinguishes itself from list_pages/read_page by scope (searches all pages) but never explicitly names a sibling or when to prefer each.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use or when-not-to-use guidance. It never tells the agent to use search when hunting for unknown content versus read_page for a known page, nor does it mention any alternatives. Only implicit usage is conveyed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.