Lazada Community MCP

Show Grocery Choices

render_product_picker

Read-onlyIdempotent

Display a saved shortlist as a comparison table with labelled product-photo cards, enabling side-by-side product review before checkout. Call after shortlisting products to present visual comparisons.

Instructions

Display a saved shortlist as a comparison table followed by labelled product-photo cards in clients supporting MCP Apps. Call after shortlist_products for comparisons; do not provide only a text table when UI is supported. Plain JSON and product image URLs remain available for fallback.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`selections`	No	Restore only choices and quantities the user has already explicitly selected. This does not add anything.
`shortlist_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.1.3Sep 8, 2026

addedInput schema / properties / selections

Added value: +{
+  "description": "Restore only choices and quantities the user has already explicitly selected. This does not add anything.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "group_id": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "quantity": {
+        "maximum": 50,
+        "minimum": 1,
+        "type": "integer"
+      },
+      "url": {
+        "format": "uri",
+        "type": "string"
+      }
+    },
+    "required": [
+      "group_id",
+      "url",
+      "quantity"
+    ],
+    "type": "object"
+  },
+  "maxItems": 10,
+  "type": "array"
+}

First observedv1.1.1Sep 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds useful context about rendering UI in MCP Apps clients and preserving JSON/image-URL fallbacks, which goes beyond the structured annotations. No contradiction with annotations.

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?

Three dense sentences with no filler: first states the core behavior, second gives sequencing and UI guidance, third covers fallback. The most important information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich annotations (read-only, idempotent, non-destructive), the presence of an output schema, and a 50%-covered input schema, the description covers the essential invocation context: when to call, what UI to produce, and what fallback exists. No critical operational detail needed for correct invocation appears missing.

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?

The schema already describes the non-obvious 'selections' parameter well: it restores only explicitly selected choices and quantities, and 'does not add anything'. 'shortlist_id' is self-evident from the phrase 'saved shortlist', so the description does not need to elaborate further.

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

Purpose5/5

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

States a specific verb ('Display') and resource ('a saved shortlist') and gives the exact UI format: a comparison table followed by labelled product-photo cards. It also distinguishes itself from the sibling workflow by saying to call after shortlist_products.

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

Usage Guidelines4/5

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

Explicitly instructs when to call the tool ('Call after shortlist_products for comparisons') and when not to fall back to a plain text table in UI-capable clients. It mentions plain JSON and image URLs as a fallback, though it does not explicitly name an alternative sibling tool beyond the sequencing.

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