Co-Reading MCP

reading_import_part

Appends a base64-encoded file part to an ongoing chunked import for EPUB or plain text books.

Instructions

Append one base64 file part to an active chunked import.

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": {
      "uploadId": "<uploadId>",
      "dataBase64": "<dataBase64>"
    },
    "name": "reading_import_part"
  }
}

Input Schema

Name	Required	Description	Default
`index`	No
`uploadId`	Yes
`dataBase64`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 6, 2026

TDQS

A3.5/5.0

Behavior2/5

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

Annotations provide no behavioral hints, so the description carries the full burden. It communicates that the operation appends data and requires an active import, but it does not explain ordering, idempotency, effects of invalid uploadId, failure behavior, or what happens after the final part is appended.

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 focused sentence with no filler. It front-loads the core action and resource, making it easy to scan and quickly understand the tool's role.

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

Completeness2/5

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

For a tool with three undocumented parameters, no output schema, and no behavioral annotations, this one-liner is insufficient. It does not explain the chunk sequencing, required upload ID origin, the role of index, or what a successful append implies for the overall import workflow.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for all three parameters. It clarifies that the part is base64-encoded, which helps for dataBase64, but uploadId is only vaguely implied by 'active chunked import', and index is not explained at all.

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 uses a specific verb ('Append'), a clear resource ('one base64 file part'), and a scoping context ('an active chunked import'). This clearly distinguishes it from siblings like reading_import_begin, reading_import_finish, and reading_import_cancel.

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?

The phrase 'to an active chunked import' gives clear contextual guidance that this tool must be called after a chunked import has been started and before finish/cancel. It does not explicitly name alternatives or exclusions, but the timing is reasonably clear.

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