Skip to main content
Glama
skyispainted

Codepage Bridge MCP

by skyispainted

Read a file from the local filesystem.

Read

Read any file from the local filesystem. Supports text, images, PDFs (up to 20 pages per request), and Jupyter notebooks with line numbers.

Instructions

Reads a file from the local filesystem. You can access any file directly by using this tool. Assume this tool is able to read all files on the machine. If the User provides a path to a file assume that path is valid. It is okay to read a file that does not exist; an error will be returned.

Usage:

  • The file_path parameter must be an absolute path, not a relative path

  • By default, it reads up to 2000 lines starting from the beginning of the file. Files larger than 256KB will return an error; use offset and limit for larger files

  • When you already know which part of the file you need, only read that part. This can be important for larger files.

  • Results are returned using cat -n format, with line numbers starting at 1

  • This tool allows Claude Code to read images (eg PNG, JPG, etc). When reading an image file the contents are presented visually as Claude Code is a multimodal LLM.

  • This tool can read PDF files (.pdf). For large PDFs (more than 10 pages), you MUST provide the pages parameter to read specific page ranges (e.g., pages: "1-5"). Reading a large PDF without the pages parameter will fail. Maximum 20 pages per request.

  • This tool can read Jupyter notebooks (.ipynb files) and returns all cells with their outputs, combining code, text, and visualizations.

  • This tool can only read files, not directories. To read a directory, use an ls command via the Bash tool.

  • You will regularly be asked to read screenshots. If the user provides a path to a screenshot, ALWAYS use this tool to view the file at the path. This tool will work with all temporary file paths.

  • If you read a file that exists but has empty contents you will receive a system reminder warning in place of file contents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoThe number of lines to read. Only provide if the file is too large to read at once.
pagesNoPage range for PDF files (e.g., "1-5", "3", "10-20"). Only applicable to PDF files. Maximum 20 pages per request.
offsetNoThe line number to start reading from. Only provide if the file is too large to read at once
file_pathYesThe absolute path to the file to read
Behavior5/5

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

No annotations are provided, so the description carries full burden. It comprehensively discloses behaviors: default 2000 lines, 256KB limit, cat -n output, multimodal for images, PDF pagination rules, notebook handling, directory exclusion, and empty file warning.

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?

Well-structured with a clear opening and bullet points. Every sentence serves a purpose, but the description is somewhat lengthy. Front-loaded with the main purpose.

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?

Given the tool's complexity and no output schema, the description is remarkably complete. It covers all parameters, edge cases (empty file, directory, screenshots), and special file types (images, PDF, notebooks). No gaps identified.

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%, so baseline is 3. The description adds significant value beyond schema: file_path must be absolute, limit only for large files, pages only for PDF, offset as line number. It also provides context like defaults and error conditions.

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 reads files from the local filesystem, with specific verb and resource. It distinguishes from sibling tools (Edit, Grep, Write) by focusing solely on reading. The title and description are aligned.

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?

Extensive guidelines are provided: absolute path requirement, default line limit, file size handling, PDF and notebook specifics, and directory exclusion. However, it does not explicitly state when to use this tool over alternatives, though the sibling names imply differentiation.

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