jambavan

Overview Schema Source Related Servers Discussions Admin

search

Find specific text in project files via regex search with ripgrep. Filter by glob, path, and case to pinpoint matching lines.

Instructions

Search project files using ripgrep, with grep fallback. Fast regex search. Paths are confined to the project root unless JAMBAVAN_ALLOW_OUTSIDE_ROOT=1.

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>"
    },
    "name": "search"
  }
}

Input Schema

Name	Required	Description
`path`	No	Directory or file to search in (default: project root)
`pattern`	Yes	Regex pattern to search
`max_results`	No	Max matching lines to return (default: 50)
`file_pattern`	No	Glob to filter files, e.g. "*.ts"
`case_sensitive`	No	Case sensitive search (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Without annotations, description discloses fast regex search, grep fallback, and path restrictions. No contradiction, but could mention result format or performance implications.

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?

Two sentences, front-loaded with core purpose, zero waste. Achieves high information density.

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?

Missing output schema and annotations, but description covers core functionality, fallback, and constraints. Could describe return structure (e.g., matching lines and paths) but adequate.

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 100% with parameter descriptions. Description adds default values (max_results: 50) and default path (project root), supplementing schema well.

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?

Description clearly states 'Search project files using ripgrep, with grep fallback' - specific verb and resource, distinguishes from sibling tools (e.g., list_files, memory_search).

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

Usage Guidelines4/5

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

Provides path confinement rule and environment variable override, guiding usage. Does not explicitly state when not to use or compare to alternatives, but context is clear.

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