asalbanoo-mcp

Overview Schema Source Related Servers Discussions Admin

Browse a category or brand

ab_browse

Read-onlyIdempotent

Browse and filter products by category, brand, price, stock, and attributes, with sorting, to find items like cheapest shampoo for oily hair or Graph brushes under 800,000 Toman.

Instructions

List the products of a category or brand (or the whole shop) with sorting, price range, stock and attribute filters.

Use for "cheapest shampoo for oily hair", "Graph brushes under 800,000 Toman", "newest sunscreens". Pass a category slug (ab_categories), a brand slug (ab_brands), both, or neither (whole shop). Attribute filters (volume, hair/skin type, gender, origin) come from ab_filters. Variable products show their cheapest variant as final_price and max_price as the top of the range. Details: ab_product; reviews: ab_reviews.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Page number, from 1.
`sort`	No	Order of the listing. 'default' puts in-stock items first (relevance for a search).	default
`brand`	No	Brand slug from ab_brands, e.g. 'graph' or 'la-roche-posay'.
`limit`	No	Products per page.
`filters`	No	Attribute filters from ab_filters: attribute -> values (any of them matches), e.g. {'bulk': ['250-میلی-لیتر'], 'hair': ['چرب']}.
`category`	No	Category slug from ab_categories, e.g. 'hair-shampoo' or 'sunscreen'.
`max_price`	No	Maximum current price in Toman, e.g. 2000000.
`min_price`	No	Minimum current price in Toman, e.g. 1000000.
`on_sale_only`	No	Only discounted items.
`in_stock_only`	No	Only items that can be ordered now.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so safety is covered. The description adds non-obvious behavior: 'Variable products show their cheapest variant as final_price and max_price as the top of the range', plus which sibling to consult for filters and details.

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?

Front-loaded with purpose and scope, then examples, then slug sourcing, then edge-case behavior. Every sentence carries information; nothing is redundant with the schema.

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?

Covers purpose, filter vocabulary sources, cross-tool routing, and the one ambiguous return-value behavior, with an output schema present to carry the rest. An agent has everything needed to call this correctly.

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 schema already documents all 10 parameters (baseline 3). The description still adds value beyond it: price units in Toman, the attribute-filter shape sourced from ab_filters, and the variant-price semantics of final_price/max_price.

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?

Opens with a specific verb+resource+scope: 'List the products of a category or brand (or the whole shop)' and enumerates the filter dimensions. It also names the sibling tools that supply inputs and drill-downs (ab_categories, ab_brands, ab_filters, ab_product, ab_reviews), so an agent can place it in the tool graph without opening schemas.

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?

Gives concrete natural-language queries it serves ('cheapest shampoo for oily hair', 'Graph brushes under 800,000 Toman') and explains that category, brand, both, or neither may be passed. It does not explicitly contrast with the closest siblings ab_search and ab_find_cheapest, so the routing for search-style requests is left to inference.

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

Deploy Server