Skip to main content
Glama

ck_fs_grep

Search file contents inside a project root using grep-style pattern matching. Returns matching lines with file paths and line numbers. Supports regex or literal strings, case-insensitivity, and scoped paths.

Instructions

Search file contents inside the bound project root using grep-style pattern matching. Read-only — no files are modified. query is a regex pattern by default; set fixed_strings: true to match literal text without regex. Scope the search with path (a relative directory or glob); omit to search the entire project. Returns matching lines with file path and line numbers. limit caps results (default 50). Use ck_fs_grep to find code patterns or strings inside files. Use ck_fs_find to locate files by name fragment. Use ck_fs_read to read a specific file by path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fixed_stringsNo
ignore_caseNoWhen true, perform case-insensitive matching.
limitNoMaximum number of results to return.
pathNoFile or directory path relative to the project root.
project_rootNoAbsolute path to the project root directory on the local filesystem.
queryYesSearch query string for filtering or full-text search.
session_idNoUnique session identifier for correlating findings, proofs, budget, and audit trail.
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses read-only nature, regex default, fixed_strings option, path scoping, return format (lines with file path and line numbers), and default limit of 50. Does not mention case sensitivity (covered in schema) or recursion behavior, but overall transparent.

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?

Concise and well-structured: opens with purpose, then details options and behavior, and ends with sibling guidance. Every sentence adds value, no redundancy.

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

Completeness5/5

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

No output schema, but description explains return values (matching lines with file path and line numbers). Covers all key aspects of input, behavior, and result for a search tool. Complete for the intended use.

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 description coverage is 86%, but description adds meaning: explains query is regex by default and fixed_strings: true changes to literal; path is relative dir/glob, omit for entire project; limit caps results. Adds context beyond schema entries.

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?

Clearly states it searches file contents using grep-style pattern matching. Distinguishes from sibling tools ck_fs_find and ck_fs_read by specifying what each tool is for.

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?

Explicitly states when to use this tool vs alternatives: 'Use ck_fs_grep to find code patterns or strings inside files. Use ck_fs_find to locate files by name fragment. Use ck_fs_read to read a specific file by path.'

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aryaminus/controlkeel'

If you have feedback or need assistance with the MCP directory API, please join our Discord server