Skip to main content
Glama
Nstdata MCP Server

Nstdata MCP Server

Official
by nstdata-ai

nstdata_crawl_status

Read-onlyIdempotent

Read aggregate crawl progress for an existing crawl ID without polling, enabling status checks of crawls started through the server.

Instructions

Read aggregate crawl progress without polling.

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": {
      "crawlId": "<crawlId>"
    },
    "name": "nstdata_crawl_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
crawlIdYesActual id returned by nstdata_crawl_start; reuse the existing task instead of submitting another crawl.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, open-world operation. The description adds that the response is aggregate progress and involves no polling, but it does not describe what the progress includes, terminal states, or how to know when to move to result retrieval.

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 front-loaded sentence with no wasted wording. It is appropriately sized for a simple one-parameter status tool.

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?

Given the simple schema and annotations, the definition is usable, but it omits important context about what 'progress' returns and how this status call relates to retrieving final results. With no output schema, those behavioral details would need to come from the description.

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 one parameter with 100% schema description coverage, and the schema already explains that crawlId must be the id returned by nstdata_crawl_start. The description itself adds no additional parameter meaning beyond that baseline.

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 gives a specific verb and resource: 'Read aggregate crawl progress.' It clearly indicates progress rather than crawl results, but it does not explicitly name a sibling such as nstdata_crawl_read_result to sharpen the distinction.

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?

The phrase 'without polling' hints at usage but does not state when to call this tool versus checking results or starting a crawl. There is no explicit when-to-use, when-not-to-use, or alternative-tool guidance.

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