Skip to main content
Glama

Search products and price lists

em_search
Read-onlyIdempotent

Search Emalls for Iranian products by keyword, category, brand, price range, and specs to find product IDs and lowest Toman prices across shops.

Instructions

Search Emalls (Iranian price comparison) for products, with price range, category, brand, spec and sort filters.

Use it first to find a product id; each row has the lowest price in Toman and shop count. Unknown category: em_categories. Brand/spec filters: em_filters first. Then em_product, em_offers, em_compare or em_price_history.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "em_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo40 products per page.
sortNocheapest also lists accessories: pair with min_price or category_id.popular
limitNoMax products from the page.
queryNoProduct words, Persian or English, e.g. گوشی سامسونگ A17. Empty with category_id browses it.
brand_idNoBrand id from em_filters.
in_stockNoOnly products some shop has in stock.
max_priceNoToman.
min_priceNoToman.
attributesNoOption ids from em_filters; one per spec group, all must match.
category_idNoCategory id from em_categories, e.g. 39 phones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.2.0
    • changedInput schema / properties / attributes / description
      Previous value: -"Spec filter option ids from em_filters, e.g. [18179, 18194] for 8GB RAM and 256GB storage. At most one option per spec group; all must match."New value: +"Option ids from em_filters; one per spec group, all must match."
    • changedInput schema / properties / brand_id / description
      Previous value: -"Only this brand (id from em_filters for the same category)."New value: +"Brand id from em_filters."
    • changedInput schema / properties / category_id / description
      Previous value: -"Limit to a category (id from em_categories), e.g. 39 for mobile phones."New value: +"Category id from em_categories, e.g. 39 phones."
    • changedInput schema / properties / in_stock / description
      Previous value: -"Only products at least one shop has in stock."New value: +"Only products some shop has in stock."
    • changedInput schema / properties / limit / description
      Previous value: -"Max products to return from the page (1-40)."New value: +"Max products from the page."
    • changedInput schema / properties / max_price / description
      Previous value: -"Highest price in Toman, e.g. 40000000."New value: +"Toman."
    • changedInput schema / properties / min_price / description
      Previous value: -"Lowest price in Toman, e.g. 20000000."New value: +"Toman."
    • changedInput schema / properties / page / description
      Previous value: -"Page number, 40 products per page."New value: +"40 products per page."
    • changedInput schema / properties / query / description
      Previous value: -"Product words in Persian or English, e.g. گوشی سامسونگ A17 or ایسوس زنفوک. Empty to browse a whole category."New value: +"Product words, Persian or English, e.g. گوشی سامسونگ A17. Empty with category_id browses it."
    • changedInput schema / properties / sort / description
      Previous value: -"popular (most viewed, the site default), cheapest, expensive or newest. cheapest also lists accessories and manuals: pair it with min_price or a category."New value: +"cheapest also lists accessories: pair with min_price or category_id."
  2. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered; the description adds value by disclosing the row shape ('lowest price in Toman and shop count'), which is otherwise unavailable since there is no output schema. It stops short of describing result totals or pagination metadata, which are left to the schema's page/limit descriptions.

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 blocks, front-loaded with what the tool does and then the routing chain; every sentence carries actionable content. The telegraphic fragments ('Unknown category: em_categories.') are terse to the point of being slightly clipped, which costs a little readability.

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 10-parameter search tool with no output schema, the description supplies the essentials: purpose, filter scope, the id-discovery workflow, row contents, and prerequisite lookups. It could say more about result-set size and what the pagination envelope returns, but nothing critical to calling it correctly is 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?

Schema coverage is 100% and every parameter carries its own description, including cross-references to em_filters and em_categories, so the baseline is 3. The description only restates the filter categories at a high level and adds no units, formats, or interaction rules (e.g. min/max price pairing) beyond what the schema already says.

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 and resource ('Search Emalls ... for products') and enumerates the filter dimensions (price range, category, brand, spec, sort). It also identifies the domain as an Iranian price-comparison site, which lets an agent place it among em_offers, em_product, and em_compare without opening any schema.

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

Usage Guidelines5/5

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

Explicit sequencing and alternatives: 'Use it first to find a product id', 'Unknown category: em_categories', 'Brand/spec filters: em_filters first', then downstream tools em_product/em_offers/em_compare/em_price_history. Each routing decision names the sibling that handles it, covering both when to use this tool and when to defer.

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