Skip to main content
Glama
Nstdata MCP Server

Nstdata MCP Server

Official
by nstdata-ai

nstdata_crawl_read_result

Read-onlyIdempotent

Read bounded chunks of crawled page content or binary files by offset and format, so you can page through large crawl results without exceeding response limits.

Instructions

Read a bounded chunk of a Crawl storage reference. Text offsets count Unicode code points; binary offsets count bytes. Each call downloads the reference again, within the response byte limit.

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": {
      "ref": "<ref>",
      "format": "<format>"
    },
    "name": "nstdata_crawl_read_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesCopy the actual value of markdownRef, htmlRef, pdfRef, screenshotRef or rawDataRef into ref; do not use the output field name as an input key.
formatYesMust match the reference field: markdownRef uses markdown, htmlRef uses html, and so on.
lengthNoMaximum Unicode code points for markdown/html, or bytes for binary formats, in this chunk. Reduce it if the chunk exceeds the output limit.
offsetNoStart position: Unicode code points for markdown/html, bytes for binary formats. Use the preceding read result's nextOffset to continue.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnly/openWorld/idempotent annotations, it discloses two meaningful behaviors: every call re-downloads the entire reference (a cost/latency warning) and the chunk is bounded by the response byte limit. It does not mention permission requirements or error/truncation responses, so it stops short of full disclosure.

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 short, front-loaded sentences with no filler: purpose first, then unit semantics, then the cost caveat. Nothing could be removed without losing information.

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 no output schema and fully documented parameters, the description supplies the essential context an agent needs: chunking model, unit semantics, and the re-download overhead. Minor gaps remain around failure modes and how to detect the end of a reference, though nextOffset is covered in the schema.

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%, and the schema already documents offsets, length caps and the nextOffset continuation pattern, so the description's note that offsets count code points for text and bytes for binary is largely a restatement. Baseline 3 applies since the schema carries parameter meaning.

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 bounded chunk of a Crawl storage reference," which tells an agent exactly what it retrieves and that results are paginated. It does not, however, distinguish itself from siblings such as nstdata_crawl_scrape_result, leaving open which reference type belongs to which tool.

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?

Usage is only implied: the description frames the call as chunked reading and notes each call re-downloads the reference, which hints at continuation, but it never states when to choose this tool over the scrape/pages siblings or when to stop iterating chunks.

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