AiLinkAny

Read a paged remote task result

get_task_result_chunk

Read-onlyIdempotent

Reads one bounded character slice from a large completed task result. Use only when a device tool or get_task_result returned result_mode=PAGED. Reuse the same command_id and advance offset with next_offset; never resubmit the original operation just to obtain more output.

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": {
      "command_id": "<command_id>"
    },
    "name": "get_task_result_chunk"
  }
}

Input Schema

Name	Required	Description
`length`	No	Maximum characters to return in this chunk.
`offset`	No	Character offset into the serialized result. Defaults to 0.
`command_id`	Yes	The command_id of the completed task.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`eof`	Yes
`chunk`	Yes
`length`	Yes
`offset`	Yes
`status`	Yes
`command_id`	Yes
`next_offset`	Yes
`total_bytes`	Yes
`total_chars`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds genuinely non-obvious operational behavior: this is a continuation loop over a single completed result, keyed by the same command_id, and the correct progression is to advance by next_offset rather than re-running the task. It stops short of saying what happens on an exhausted or invalid command_id, which keeps it from a 5.

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?

Three sentences, each load-bearing: what it does, when to use it, and how to drive it. The restrictive condition and the prohibition on resubmission are front-loaded, with no filler or restatement of the title.

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?

With full schema coverage, complete annotations, and an output schema presumably carrying next_offset, the definition covers everything an agent needs to page correctly. Minor gap: it does not state terminal/error behavior (end of result, unknown command_id), though the output schema likely covers that.

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?

Schema coverage is 100%, so offset/length/command_id definitions are already documented, establishing a baseline of 3. The description goes beyond that by explaining the relationship between the parameters across calls: command_id must be reused unchanged and offset must be advanced from next_offset, which is operational meaning the schema alone does not convey.

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 states a specific verb and resource ('Reads one bounded character slice from a large completed task result') and immediately scopes it against the sibling get_task_result by naming the result_mode=PAGED condition. An agent can distinguish it from get_task_result without opening either schema.

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

Usage Guidelines5/5

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

It gives an explicit trigger (only when a device tool or get_task_result returned result_mode=PAGED), an explicit anti-pattern (never resubmit the original operation just to obtain more output), and the correct continuation procedure. When-to-use, when-not-to-use, and the alternative are all present.

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

All AiLinkAny tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?