Find code nodes using lexical or semantic retrieval to give AI coding assistants precise context, reducing token usage and avoiding outdated or irrelevant files.
Search CodeNodes using the configured lexical or semantic retrieval mode.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.1.1Does 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 that the lexical or semantic retrieval mode is configured externally rather than selected per call, but it does not state read-only status, permissions, rate limits, or other behavioral constraints.
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?
The description is a single front-loaded sentence with no wasted wording. Every phrase contributes to identifying the operation and retrieval mode.
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?
Although an output schema exists, so return values need not be explained, the description is incomplete for a tool with 0% schema description coverage and no annotations. It omits query semantics and usage context, making it hard for an agent to know how to phrase the query or when to select this tool.
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 description coverage is 0%, and the sole parameter is undocumented beyond its title 'Query.' The verb 'Search' minimally implies that the parameter is a search term, but the description adds no syntax, format, or mode-dependent query guidance.
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?
The description states a specific verb and resource: 'Search CodeNodes.' It also specifies that retrieval uses a configured lexical or semantic mode, distinguishing it from generic context tools, though it does not name any sibling alternatives.
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?
The description gives no explicit when-to-use guidance, prerequisites, or alternatives. It only implies that the tool is for searching code, leaving the agent to infer when this is preferable to tools like get_symbol_context or get_file_context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.