asalbanoo-mcp

Overview Schema Source Related Servers Discussions Admin

Browse a category or brand

ab_browse

Read-onlyIdempotent

List cosmetics shop products by category or brand, apply price, stock and attribute filters, and sort results to find items like budget shampoo or brushes under a price.

Instructions

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

Use for "cheapest shampoo for oily hair", "Graph brushes under 800,000 Toman". Pass a category slug (ab_categories), a brand slug (ab_brands), both, or neither; filters come from ab_filters. Details: ab_product; reviews: ab_reviews.

Input 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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv0.3.0Oct 17, 2026
- removedInput schema / properties / brand / title
```
Removed value: -"Brand"
```
- removedInput schema / properties / category / title
```
Removed value: -"Category"
```
- removedInput schema / properties / filters / title
```
Removed value: -"Filters"
```
- removedInput schema / properties / in_stock_only / title
```
Removed value: -"In Stock Only"
```
- changedInput schema / properties / limit / default
```
Previous value: -24New value: +20
```
- removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```
- removedInput schema / properties / max_price / title
```
Removed value: -"Max Price"
```
- removedInput schema / properties / min_price / title
```
Removed value: -"Min Price"
```
- removedInput schema / properties / on_sale_only / title
```
Removed value: -"On Sale Only"
```
- removedInput schema / properties / page / title
```
Removed value: -"Page"
```
- removedInput schema / properties / sort / title
```
Removed value: -"Sort"
```
- removedInput schema / title
```
Removed value: -"ab_browseArguments"
```
- changedOutput schema / (root)
```
Previous value: -{
-  "additionalProperties": true,
-  "title": "ab_browseDictOutput",
-  "type": "object"
-}New value: +null
```
First observedv0.1.0Oct 6, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already cover the safety profile thoroughly (readOnly, idempotent, openWorld, non-destructive), lowering the bar. The description adds useful behavioral context that listings default to in-stock-first ordering, but does not disclose pagination limits, how the maxProperties=5 filter cap behaves, or result-count semantics.

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?

The core purpose is front-loaded in the first sentence, followed by examples and then sibling routing in a compact three-block layout. Slightly dense but every element (examples, slug provenance, routing) earns its place.

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, all-optional browse tool with no output schema and rich annotations, the description covers purpose, examples, input provenance and sibling routing adequately. Minor gaps remain around pagination behavior and how multiple filters compose, but nothing an agent needs to call it correctly is missing.

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, but the description adds real value beyond the schema by naming the upstream tools that supply valid category, brand and filter values. It does not explain how category+brand combine or how filters interact with the price range, so it does not reach a 5.

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

Purpose4/5

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

States a specific verb and resource ('List products of a category or brand') plus the scope of filters, and gives concrete query examples. It partially distinguishes itself by routing to ab_product and ab_reviews, but never explains how it differs from ab_search or ab_find_cheapest, even though the example 'cheapest shampoo for oily hair' overlaps heavily with those siblings.

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 explicit usage examples and the key routing rule that slug inputs must come from ab_categories, ab_brands and ab_filters, which tells the agent the correct call sequence. It stops short of stating when to prefer ab_search or ab_find_cheapest instead, so the most important boundary for this tool 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

Browse a category or brand

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools