BytNode

Read Export

read_export

Read-only

The rest of a response cut by its size budget, page by page, same format, free. key: as in its data (default the first); offset: first row (0 = newest; the cut response's ranges..row_count). next_offset null = end. One hour, same API key.

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": {
      "export_id": "<export_id>"
    },
    "name": "read_export"
  }
}

Input Schema

Name	Required	Description
`key`	No	Series key (default the first).
`offset`	No	First row (0 = newest).
`export_id`	Yes	export.export_id of the cut response.
`max_tokens`	No	Response budget, estimated tokens (default 6000).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare this a read-only, non-destructive operation, so the bar is lower, yet the description still adds real behavior: the continuation is 'free' (no budget consumed) and is valid for 'One hour, same API key,' implying a short-lived export session tied to the original key. Both points are terse and slightly ambiguous ('One hour' has no stated subject), but they are genuinely beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the paging concept, with no filler sentences. However, the semicolon-separated shorthand and subjectless fragments ('One hour, same API key') make it harder to parse than plain sentences would, so it is compact at the cost of structure.

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?

For a four-parameter continuation tool with no output schema, the paging loop and stopping condition are covered, which is the essential part. Gaps remain around what 'One hour' applies to (export lifetime vs. pagination window), what happens on expiry, and what a page actually returns, all of which the agent must infer.

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 a 3 is the baseline, but the description adds meaning the schema does not: offset is sourced from the cut response's ranges.<key>.row_count, 0 means newest, and key defaults to the first series. It also introduces next_offset as the termination signal, which is not a parameter and would otherwise be invisible.

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?

The description says this returns 'the rest of a response cut by its size budget, page by page, same format,' which makes the resource (a truncated export's remainder) and the paging behavior identifiable. It lacks an explicit verb and never names a sibling, but no sibling in the catalog performs continuation, so confusion risk is low.

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 trigger for use is implied clearly: a response was cut by its size budget, so call this to continue. It further tells the agent to take offset from 'the cut response's ranges.<key>.row_count' and to stop when 'next_offset null = end,' which is concrete loop guidance. It stops short of naming exclusions or alternative tools.

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

All BytNode 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?