Skip to main content
Glama
aliyun-agent-sandbox-mcp

aliyun-agent-sandbox-mcp

Read a file

file_read
Read-only

Read text files from a sandbox and page through large files by specifying line offset and limit.

Instructions

Read a text file from the sandbox. Use offset/limit to page through large files.

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": "file_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path inside the sandbox, e.g. /home/user/main.py.
limitNoMaximum number of lines (default 2000).
offsetNo0-based line offset (default 0).
sandbox_idNoSandbox ID, e.g. sbx-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (returned by sandbox_create).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds the sandbox scoping constraint and the fact that only text files are supported, which is genuinely useful, but it says nothing about behavior on missing paths, permission errors, or what the returned content looks like.

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?

Two short sentences with zero filler, and the core action is front-loaded before the paging tip. Efficient, though the extreme brevity leaves the description thin on behavior relative to the tool's 4 parameters.

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

Completeness3/5

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

With 100% schema coverage and annotations present, most structured information is covered, but there is no output schema and the description never indicates what a read returns (raw text, line numbering, truncation signaling). For a paging-capable read tool, that leaves a meaningful gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so path, limit, offset, and sandbox_id are already documented with defaults and bounds. The description only adds the purpose of offset/limit (paging through large files), which is marginal value over the schema's own 'Maximum number of lines' and '0-based line offset' descriptions.

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?

States a specific verb and resource ('Read a text file from the sandbox') and implicitly scopes out writing, listing, and deletion handled by siblings like file_write and file_list. The 'text file' qualifier is a useful scope boundary, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

The second sentence gives actionable guidance for one case: paging through large files with offset/limit. It offers no guidance on when to prefer this over alternatives such as file_list or run_command, nor any prerequisites about the sandbox being alive.

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