cascade-mcp

cascade_remote_read

Read files from an opened remote target using a READY handle, with optional offset and limit to fetch specific line ranges with line numbers.

Instructions

Read a file from an opened remote target. Requires a READY handle returned by cascade_target open. Supports offset & limit with line numbers.

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

Input Schema

Name	Required	Description
`path`	Yes	Remote file path
`limit`	No	Number of lines to read
`handle`	Yes	READY target handle (e.g. target-1)
`offset`	No	Starting line number (1-based)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 29, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the READY-handle precondition and the offset/limit line-based read model, but does not state read-only semantics, behavior on an invalid handle, or what a failed read returns. Useful but incomplete disclosure for a read operation.

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?

Three short sentences with the core purpose and the handle prerequisite front-loaded; nothing is padded. It is terse enough that a little more detail could fit without harming readability.

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?

There is no output schema, so the description should carry return-value expectations; it only hints at numbered lines via 'with line numbers' and says nothing about error or empty-file behavior. Adequate for invoking the tool, but thin for a tool with no structured return contract.

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 coverage is 100%, with each of the four parameters documented (path, limit, handle, offset 1-based) directly in the schema. The description's 'offset & limit with line numbers' merely restates what the schema already provides, so the baseline 3 applies.

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 file from an opened remote target'), which clearly separates it from sibling listing/search operations like cascade_remote_ls, grep, and find. However, it does not explicitly name any sibling or contrast itself beyond the implicit file-contents scope.

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?

Provides a real prerequisite ('Requires a READY handle returned by cascade_target open'), which tells the agent when the tool is usable. It offers no when-not guidance and does not route the agent to alternatives such as cascade_remote_grep for searching or cascade_remote_ls for listing, so usage is only partially framed.

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

Deploy Server