Skip to main content
Glama
Sign In
E2B MCP Server

E2B MCP Server

by parth012001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

read_file

Retrieve file contents from a secure cloud sandbox to inspect outputs, logs, or configuration files during code execution.

Instructions

Read a file from the sandbox environment

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": {
      "path": "<path>"
    },
    "name": "read_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesFile path to read
sandbox_idNoOptional sandbox ID to use specific sandbox

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'read', which implies no side effects, but it does not explain what is returned, how missing files are handled, or how sandbox_id affects behavior. This is a minimal disclosure for a tool with no annotation support.

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 a single front-loaded sentence with no filler or redundant detail. Every word contributes meaning, and the core action is immediately clear.

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?

For a simple read operation with only two parameters, the description is largely sufficient. It lacks an explicit statement of return value and error behavior, but given the tool's simplicity and the fully covered schema, the remaining gaps are minor.

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?

The schema fully documents the two parameters, so the baseline is 3. The description adds useful context by specifying that the path refers to a file inside the sandbox environment, which is not stated in the schema's 'File path to read' property. This small semantic addition raises it to 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb ('read') and resource ('file from the sandbox environment'), making it easy to distinguish from siblings like create_file and list_files. It does not explicitly name the sibling alternatives, so it stops short of a 5, but the purpose is unambiguous.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as list_files or execute_python. The description implies reading a file's contents, but it gives no exclusions, prerequisites, or comparison to sibling tools.

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

Deploy Server

Other Tools