gemini-cli-bridge

Overview Schema Source Related Servers Discussions Admin

Searchtext

SearchText

Search for a text pattern within a file and return matching lines with line numbers and text as JSON. Supports optional case-insensitive matching.

Instructions

Search text within a file; return JSON array [{line, text}].

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": {
      "pattern": "<pattern>",
      "path": "<path>"
    },
    "name": "SearchText"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`pattern`	Yes
`case_insensitive`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Oct 20, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden, and it delivers little: it does not say whether `pattern` is a literal substring or a regular expression, whether matching is per-line, whether large files are truncated, or what happens on no matches. It only discloses the return shape, which the output schema already covers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact, front-loaded sentence with no filler. The return-shape clause is largely redundant given the output schema, but it costs little and is tucked at the end rather than leading.

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

Completeness2/5

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

The output schema excuses the description from explaining return values, and it has a 3-param surface. Still, the ambiguities that would most change how an agent calls it — regex vs. literal matching, path-target constraints, case sensitivity — are absent from both schema and description, leaving the tool under-specified.

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

Parameters2/5

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

Schema description coverage is 0% across all 3 parameters, so the description must compensate — but it says nothing about `path` (file vs. directory), nothing about whether `pattern` is regex or literal, and never mentions `case_insensitive` or its default. The word 'text' offers only the faintest hint about pattern semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Search) and resource (text within a file), which distinguishes it from ReadFile, FindFiles, and Shell for the likely use case. However, it does not explicitly differentiate itself from grep-via-Shell or from FindFiles, so it falls short of a 5.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no mention of the sibling alternatives (FindFiles for filename matching, Shell for general-purpose grep, ReadFile for full contents), and no prerequisites. The agent must infer the routing entirely from the name.

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