Skip to main content
Glama
Nstdata MCP Server

Nstdata MCP Server

Official
by nstdata-ai

nstdata_crawl_scrape_result

Read-onlyIdempotent

Resume a submitted single-page scraping task by task ID to retrieve results; failed or expired tasks are reported explicitly.

Instructions

Resume a submitted single-page task. Processing is not completion; a failed or expired task is reported explicitly.

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": {
      "taskId": "<taskId>"
    },
    "name": "nstdata_crawl_scrape_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYesActual id returned by an existing single-page submission; not a site crawl id or a storage reference.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, openWorld), and the description adds real semantics beyond them: "Processing is not completion" warns that a returned state may be in-flight, and failures or expiry are surfaced explicitly rather than silently. It still omits whether the call blocks or must be polled, but the state-model disclosure is a genuine addition.

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

Conciseness4/5

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

Two short sentences with no filler, and the action statement is front-loaded ahead of the caveat. The caveat sentence is compressed to the point of being slightly cryptic, but nothing is wasted.

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 one-parameter, no-output-schema tool the definition is serviceable, but it leaves unresolved how the agent should distinguish this from read_result/status or how to interpret the returned state after "processing." Adequate, not complete.

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?

There is a single required parameter with 100% schema coverage, and the schema already explains that taskId must be the id from a single-page submission, not a crawl id or storage reference. The description adds no further meaning about the parameter, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Resume a submitted single-page task" gives a verb and a resource, and the name suggests it retrieves scrape output, but the description never says it returns results or how it differs from nstdata_crawl_read_result or nstdata_crawl_status. The agent must infer the outcome from the tool name rather than the description.

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

Usage Guidelines2/5

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

"Resume a submitted single-page task" implies it follows a prior submission, but there is no explicit when-to-use guidance, no condition selecting it over the sibling result/status tools, and no note on how often to call it.

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