Skip to main content
Glama

ck_fs_grep

Read-onlyIdempotent

Search file contents in your project using grep-style patterns. Supports fixed-string or regex search, scoped by directory or glob, and returns matching lines with file paths and line numbers.

Instructions

Search file contents inside the bound project root using grep-style pattern matching. Read-only — no files are modified. query uses fixed-string search by default; set fixed_strings: false to treat it as a 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
pathNoFile or directory path relative to the project root.
limitNoMaximum number of results to return.
queryYesSearch query string for filtering or full-text search.
session_idNoUnique session identifier for correlating findings, proofs, budget, and audit trail.
ignore_caseNoWhen true, perform case-insensitive matching.
project_rootNoAbsolute path to the project root directory on the local filesystem.
fixed_stringsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
totalNo
matchesNo
Behavior4/5

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

Description adds 'Read-only — no files are modified' which matches annotations (readOnlyHint, idempotentHint, destructiveHint). Additional context on default fixed_strings behavior is useful beyond annotations.

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?

Six well-structured sentences: purpose, safety, parameter details, return info, limits, and sibling differentiation. No unnecessary words, front-loaded with key info.

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?

Covers main use cases, scope, defaults, and differentiation. Does not detail output schema but that exists. Missing some parameter guidance (e.g., ignore_case) but overall sufficient for a 7-parameter tool with good annotations.

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 86%; description adds meaning for query (default fixed-string, can be regex), limit (default 50), and path (relative directory/glob). This goes beyond schema descriptions.

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 file contents using grep-style pattern matching' and distinguishes from siblings by naming ck_fs_find and ck_fs_read with their specific uses. Verb and resource are specific.

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 tells when to use this tool ('find code patterns or strings inside files') and when to use alternatives (ck_fs_find for name, ck_fs_read for specific file). Also explains scoping with path and default fixed-string search.

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