Search indexed source files using regex to locate strings, config keys, and dynamic names the symbol index misses. Filter results by glob patterns.
Regex search over indexed source files (smart case). glob like '.ts' or 'backend/'. Use for strings, config keys and dynamic names the symbol index cannot see.
| Name | Required | Description | Default |
|---|---|---|---|
| glob | No | ||
| limit | No | ||
| pattern | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It usefully discloses 'smart case' matching and that files must be indexed, but does not explicitly state that the operation is read-only or describe indexing prerequisites or rate/output behavior.
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?
Three short sentences, front-loaded with the core action and followed by parameter examples and usage guidance. Every sentence adds distinct value.
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?
An output schema exists, so return values need not be described. The description adequately covers the main search behavior and glob parameter, though the undocumented limit parameter and lack of indexing prerequisites keep it from being fully complete for a 3-parameter search 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%, so the description must compensate. It gives helpful glob examples ('*.ts' or 'backend/*') and indicates the pattern is regex, but does not explain the limit parameter or provide more pattern syntax detail.
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 (regex search) and resource (indexed source files), and distinguishes itself from symbol-index siblings by noting it finds strings, config keys, and dynamic names the symbol index cannot see.
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?
Clearly identifies the use case: strings, config keys, and dynamic names not visible to the symbol index. It implies the alternative (symbol lookup) but does not name a specific sibling tool or provide explicit when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.