Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pandamart_store_search

Search a specific pandamart darkstore's full catalog by keyword to find available products with real prices, stock, and availability, including pagination details.

Instructions

Search for products within one pandamart darkstore. Searches by keyword within one darkstore's own catalog -- the pandamart equivalent of the search box on a darkstore page. Unlike the product showcase's curated shelves, this reaches the store's full catalog by keyword. Returns matching products with real prices, stock, and availability, plus total_products and has_more for pagination via page/limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesDarkstore code, from /pandamart/search's code field
pageNo1-based result page (default 1)
sortNoResult order. One of RELEVANCE, PRICE_ASC, PRICE_DESC. Defaults to RELEVANCE.
limitNoProducts per page, clamped to 10-50 (default 20)
queryYesProduct search text
marketNoDelivery Hero market the store belongs to. One of sg, pk, bd, hk, my, ph. Defaults to sg.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / market / enum
      Added value: +[
+  "sg",
+  "pk",
+  "bd",
+  "hk",
+  "my",
+  "ph"
+]
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "RELEVANCE",
+  "PRICE_ASC",
+  "PRICE_DESC"
+]
  2. Addedv1.16.2

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are present, so the description carries the full burden. It discloses return fields (real prices, stock, availability, total_products, has_more) and pagination behavior. It also clarifies the scope (one darkstore) and keyword-based search. No side effects or auth requirements are mentioned, but for a read-only search tool this is acceptable.

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 sentences with no redundancy. The purpose is stated first, then the contrast with curated shelves, and finally the return structure. Every sentence earns its place and the description is front-loaded.

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 search tool with no output schema, the description covers the key behavior, return fields, and pagination. The schema handles parameter details. It is complete enough for an agent to call correctly, though it could have explicitly mentioned that the code must come from a pandamart search result, but that is in the schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds value beyond the schema by explaining how page/limit relate to total_products/has_more for pagination, and by emphasizing that it searches the full catalog by keyword. This clarifies the usage of the query and pagination parameters beyond their individual schema descriptions.

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?

The description states a specific verb ('Search for products within one pandamart darkstore'), identifies the resource (darkstore catalog), and explicitly contrasts with the product showcase's curated shelves. This makes the tool's purpose distinct from siblings like pandamart_store_products or pandamart_store_categories.

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?

It clearly differentiates from the 'product showcase's curated shelves' and explains this reaches the full catalog by keyword. It also mentions pagination via page/limit, implying when to use that. However, it doesn't name the exact sibling tool for curated shelves, leaving a slight inference gap.

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

Deploy Server

Other Tools