Skip to main content
Glama

Nexscope Ecommerce Data MCP

Nexscope aliexpress access task result

nexscope_aliexpress_access_task_result
Read-onlyIdempotent

Read an AliExpress access 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_access_task_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine value beyond them by clarifying that no new supplier request is submitted and no credits are charged. It does not disclose what happens if the task is still pending, if the taskId belongs to another user, or what the result payload looks like.

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, front-loaded sentences with no filler; the scope statement comes first and the cost/side-effect caveat second. Slightly repetitive of the title's framing but otherwise efficient.

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 simple single-parameter read tool this is close to adequate, and annotations cover the safety profile. With no output schema, however, the description leaves the return shape entirely unexplained — an agent cannot tell whether it receives a status, a result payload, or a pending indicator.

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?

There is a single required parameter with 0% schema description coverage, so the description must carry the semantic load and does not mention taskId at all. The schema at least specifies format uuid and required status, which keeps this above a 1, but no meaning is added about where a taskId comes from or what it identifies.

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 uses a specific verb plus resource ("Read an AliExpress access task") and adds scope ("owned by the current user"). It is clear what the tool does, though it does not explicitly differentiate itself from the similarly named sibling nexscope_aliexpress_task_result.

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 clause "This does not submit another supplier request or charge credits" implies the appropriate context (retrieving an already-created task rather than starting new work) and gives a useful negative boundary. However, there is no explicit statement of when to call this versus the near-identical sibling result tool, leaving routing to inference.

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