Skip to main content
Glama

Nexscope Ecommerce Data MCP

1688 Order Detail

nexscope_data_alibaba1688_order_detail
Read-only

Read an order belonging to the current 1688 buyer, including orders placed directly on 1688. Uses the currently authenticated Nexscope user's 1688 buyer authorization. Orders are read live through the existing 1688 connection. The buyer identity comes from the server, and results are not cached.

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": {
      "aliOrderId": "<aliOrderId>"
    },
    "name": "nexscope_data_alibaba1688_order_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
aliOrderIdYesPositive 1688 order ID; send as a JSON string to preserve precision.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), and the description adds genuinely new context: authorization comes from the authenticated Nexscope user's 1688 buyer grant, buyer identity is resolved server-side, reads are live, and results are not cached. It stops short of describing failure behavior for an unknown or unauthorized order ID.

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

Conciseness3/5

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

Four sentences with some redundancy: "uses the currently authenticated Nexscope user's 1688 buyer authorization" and "buyer identity comes from the server" overlap, as do "read live through the existing 1688 connection" and "results are not cached." The core statement is front-loaded, but the middle sentences repeat themselves.

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?

For a one-parameter read tool whose annotations already declare its safety profile and whose parameter is fully documented in the schema, the description covers the remaining unknowns an agent needs: auth source, identity resolution, and data freshness. Return shape is unspecified, but no output schema exists and the description does not need to enumerate fields for a lookup this narrow.

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 aliOrderId thoroughly, including the positive-integer pattern and the instruction to send it as a string to preserve precision. The description adds no further meaning about the parameter, so the baseline of 3 applies.

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?

"Read an order belonging to the current 1688 buyer" gives a specific verb and resource, and the clause about orders placed directly on 1688 scopes which orders qualify. It does not explicitly contrast itself with siblings such as order_list, order_preview, or order_status, so the detail-vs-list distinction is left to the agent's inference from the name.

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 single-order framing implies "use when you already have an order ID," but the description never says when to prefer this over order_list, order_status, or order_preview, nor does it state prerequisites such as needing an active 1688 connection. Usage is inferable rather than stated.

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