Skip to main content
Glama
skyispainted

Codepage Bridge MCP

by skyispainted

A powerful search tool built on regular expressions.

Grep

Search file contents using regular expressions with support for glob filters, file types, context lines, and multiline matching. Handles legacy encoded files transparently.

Instructions

A powerful search tool for file contents.

Usage:

  • ALWAYS use Grep for search tasks. NEVER invoke grep or rg as a Bash command.

  • Supports full regular expressions, file glob filters, file type filters, context lines, match-only output, multiline matching, pagination, file lists, and per-file counts.

  • Use output_mode=files_with_matches when you only need file paths; this is the default.

  • Use output_mode=content to see matching lines. Line numbers are included by default.

  • Use output_mode=count to see match counts per file.

  • Results are limited to 250 entries by default; use head_limit and offset for pagination.

  • Every file is decoded according to its nearest project .encoding-rules, so legacy encoded content is searched as Unicode transparently.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
-ANoShow lines after each match
-BNoShow lines before each match
-CNoShow lines before and after each match
-iNoCase-insensitive search
-nNoShow line numbers in content mode. Defaults to true.
-oNoPrint only matching non-empty parts of each line
globNoGlob pattern used to filter files, for example *.js or **/*.ts
pathNoFile or directory to search. Defaults to the current working directory.
typeNoFile type filter such as js, ts, py, rust, go, or java
offsetNoSkip the first N result lines or entries
contextNoAlias for -C
patternYesThe regular expression pattern to search for in file contents
multilineNoEnable multiline matching where dot also matches newlines
head_limitNoLimit returned lines or entries. Defaults to 250; 0 means unlimited.
output_modeNoOutput mode. Defaults to files_with_matches.
Behavior5/5

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

No annotations provided, but the description fully discloses behavior: result limits (250), pagination via head_limit and offset, encoding handling, default modes, and line numbers. It implicitly indicates read-only nature.

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 well-structured with clear sections and bullet points. It is concise yet covers all necessary usage details without repetition.

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 annotations and no output schema, the description covers essential aspects: usage, parameters, defaults, encoding, and pagination. It is sufficient for an agent to invoke the tool correctly, though it could mention that output is textual.

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 has 100% coverage, so baseline is 3. The description adds value by explaining the purpose of output modes, the default for line numbers, and the effect of head_limit=0. This extra guidance justifies a 4.

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 it is a search tool for file contents using regular expressions, and explicitly differentiates from sibling tools (Edit, Read, Write) by stating it should be used for search tasks.

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?

Provides explicit usage instructions: 'ALWAYS use Grep for search tasks. NEVER invoke grep or rg as a Bash command.' Also explains when to use different output modes (content, files_with_matches, count) and pagination.

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/skyispainted/codepage-bridge-mcp'

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