Skip to main content
Glama

Nexscope Ecommerce Data MCP

Nexscope aliexpress task result

nexscope_aliexpress_task_result
Read-onlyIdempotent

Read an AliExpress collection task owned by the current user. This does not submit another supplier request or charge credits.

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": "nexscope_aliexpress_task_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive safety profile, but the description adds genuinely new behavior: no credit consumption and no re-submission of a supplier request, plus user-scoped ownership/auth. It stops short of describing what is returned when a task is still pending or has failed.

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?

Two short sentences, no filler, with the ownership scope and the cost/no-resubmit caveat front-loaded. Every sentence earns its place.

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?

With no output schema, the description should say something about what a 'task result' looks like (pending vs. complete, payload shape), and it does not. It is adequate for invocation but leaves the return-value expectation unresolved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single required parameter 'taskId' is not mentioned at all in the description. While the uuid format makes it largely self-explanatory, the description contributes nothing about where the id comes from or what a valid value looks like.

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 an AliExpress collection task') and adds ownership scoping ('owned by the current user'). It never distinguishes itself from the similarly named task-result siblings, so an agent must infer which result tool to pick, but the core purpose is unambiguous.

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?

The line 'This does not submit another supplier request or charge credits' implicitly tells the agent this is a retrieval/status step rather than a kickoff, which is useful negative guidance. It does not state prerequisites (e.g. that a task must already exist) or name any alternative tool for submitting the request.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources