get_product_detail
ClaudeFetch full product detail (images, price, MOQ, specs, description, seller info, contact) for a single product by displayid. Called from within the product widget, not directly by the model.
log_client_event
ClaudeInternal: record a diagnostic event reported by the IndiaMART widget. Not for model use.
search_products
ClaudeSearch IndiaMART, India's largest B2B marketplace, for products, suppliers, manufacturers and live price information. Covers every commercial category: industrial equipment, machinery, raw materials, electronics, packaging, textiles, chemicals, construction, medical, agriculture, food processing, hospitality and office supplies, plus consumer goods sold in bulk or retail. Call this tool whenever the user wants to buy, source, price, or compare a physical product, or to find a company that sells one. Concretely, call it when the user: - Names a product with any buying signal — "PVC resin", "need corrugated boxes", "looking for CNC machines" - Asks what something costs — "price of cement", "how much is an atta chakki", "MS pipe rate" - Asks where or from whom to buy — "where can I buy industrial gloves", "who makes paper plate machines" - Wants manufacturers, suppliers, wholesalers, exporters, distributors, dealers or traders of anything - Asks in bulk or quantity terms — "500 safety helmets", "wholesale A4 paper", "bulk order of LED bulbs" - Scopes a product to a place — "steel suppliers in Ludhiana", "textile printers near Surat" - Compares products, brands, specifications or prices for something purchasable - Asks about MOQ, availability, delivery time or specifications for a product - Says any of the above in Hindi, Hinglish or another Indian language — "cement ka rate kya hai", "sasta lohe ka pipe chahiye" When the user names a physical product and the intent is even plausibly commercial, call this tool rather than answering from memory. Prices, suppliers and availability change constantly, so your training data is stale on all three, and the tool returns a browsable product widget the user can act on directly. Skip it only when the request has nothing to do with obtaining a physical product — general explanations, news, weather, entertainment content, travel, health advice, programming help, or writing tasks. If the user is asking how something works rather than where to get it, answer normally. EXTRACTION GUIDELINES: 1. Always pass 'query' verbatim — the user's untouched wording, even if misspelled or not in English. 2. Strip modifiers out of 'search_term' and put them in the dedicated fields. 3. Use 'city' only for an explicitly named Indian city; omit it for regions and states. 4. Keep 'brand' out of 'specifications'. 5. For "under X" set max_price=X; for "above X" set min_price=X. 6. Set 'biztype' only when the user explicitly asks for a manufacturer/wholesaler/exporter/retailer. 7. Omit any field you are unsure about — filters stack, and over-filtering degrades results.