Skip to main content
Glama
JSungMin

vs-token-safer

by JSungMin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

search_text

Search source and config files with a literal string or regex, returning token-capped file:line matches for text that symbol lookup cannot resolve.

Instructions

Raw text/regex search (string literals, comments, config — what the symbol index can't answer). Replaces Bash grep when you need text, not symbols. → capped file:line: line. For code symbols prefer search_symbol.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesString or regular expression.
docsNoWith no path/glob, widen the sweep to docs/config text (md/json/yaml/…).
globNoOnly files matching this basename glob (e.g. *.md).
pathNoSearch ONE file (any extension auto-included).
maxResultsNo
projectPathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.37.3
    • changedInput schema / properties / docs / description
      Previous value: -"With no path/glob, widen the sweep to docs/config text (md/json/yaml/…), not just source."New value: +"With no path/glob, widen the sweep to docs/config text (md/json/yaml/…)."
    • changedInput schema / properties / glob / description
      Previous value: -"Only files matching this basename glob (e.g. *.md) — any extension it covers."New value: +"Only files matching this basename glob (e.g. *.md)."
    • removedInput schema / properties / maxResults / description
      Removed value: -"Result cap (60)."
    • changedInput schema / properties / path / description
      Previous value: -"Search ONE file (any extension auto-included; relative or absolute)."New value: +"Search ONE file (any extension auto-included)."
    • removedInput schema / properties / projectPath / description
      Removed value: -"Project root (cwd)."
    • changedInput schema / properties / q / description
      Previous value: -"String or regular expression to find."New value: +"String or regular expression."
  2. Changed2 schema fields changedv0.29.2
    • changedInput schema / properties / maxResults / description
      Previous value: -"Result cap (default 60)."New value: +"Result cap (60)."
    • changedInput schema / properties / projectPath / description
      Previous value: -"Project root (default cwd)."New value: +"Project root (cwd)."
  3. Changed5 schema fields changedv1.0.3
    • changedInput schema / properties / docs / description
      Previous value: -"When NO path/glob is given, widen the project-wide sweep to README/docs/config text (md/txt/json/yaml/…), not just source. Ignored when path/glob targets a file directly."New value: +"With no path/glob, widen the sweep to docs/config text (md/json/yaml/…), not just source."
    • changedInput schema / properties / glob / description
      Previous value: -"Search only files matching this basename glob (e.g. *.md, *.json) — any extension the glob covers, no docs flag needed."New value: +"Only files matching this basename glob (e.g. *.md) — any extension it covers."
    • addedInput schema / properties / maxResults / description
      Added value: +"Result cap (default 60)."
    • changedInput schema / properties / path / description
      Previous value: -"Search ONE named file (any extension — naming a README.md/.txt/etc auto-includes it; no docs flag needed). Relative to the project root or absolute."New value: +"Search ONE file (any extension auto-included; relative or absolute)."
    • addedInput schema / properties / projectPath / description
      Added value: +"Project root (default cwd)."
  4. First observed

TDQS

A4.6/5.0
Behavior4/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 discloses the output format as 'capped `file:line: line`' and mentions widening the search for docs/config text via the docs parameter. However, it lacks explicit statements about safety (read-only) or potential limitations like rate limits.

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 extremely concise: two sentences plus an arrow note. Every sentence adds value and is front-loaded with the core purpose. No fluff.

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?

Given no output schema, the description partially covers return format ('capped file:line: line'). It covers key parameters and usage context but omits details on maxResults and projectPath. For a search tool with 6 parameters, it is fairly complete but not exhaustive.

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 coverage is 67%; the description adds value beyond the schema by explaining the 'docs' parameter behavior ('widen the sweep to docs/config text') and clarifying that 'path' searches one file and 'glob' filters basename. It does not cover projectPath or maxResults, but those are somewhat self-explanatory. The total value added is moderate.

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 performs raw text/regex search, specifies the resource (text like string literals, comments, config), and distinguishes it from sibling search_symbol. The verb 'search' and resource 'text' are explicit.

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

Usage Guidelines5/5

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

The description explicitly tells when to use this tool ('when you need text, not symbols') and when not to ('For code symbols prefer search_symbol'). It also mentions it replaces Bash grep, providing clear alternatives.

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

Deploy Server

Other Tools