Read file
read_fileUse this when the task calls for plain text files on a paired computer: source code, configuration, Markdown, logs, scripts, or other line-oriented text. Use read_document instead for PDF, DOCX, XLSX and other structured document content. read_file keeps legacy PDF/DOCX extraction for compatibility but should not be the model’s first choice for those formats.
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>",
"device": "<device>"
},
"name": "read_file"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Absolute path of the file to read. Relative paths resolve against the runtime working directory. | |
| device | Yes | ReMCP device id returned by list_devices. Required for every device operation. | |
| length | No | Maximum number of lines to return. | |
| offset | No | Zero-based first line to read. Negative values read the last N lines. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | Optional structured result data for follow-up reasoning and tool calls. | |
| text | Yes | Concise human-readable result of the tool call. |