Skip to main content
Glama
sepehr071

asalbanoo-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search products

ab_search
Read-onlyIdempotent

Search cosmetics, skin, hair, and makeup products by keyword to compare prices, discounts, stock, and ratings. Filter by price or availability and sort results.

Instructions

Search products by keyword: price, discount, stock and rating of each match.

Use first for "price of X" / "do you have X". Matching is broad (title and description), so check titles. Cheapest match: ab_find_cheapest; a category or brand: ab_browse; one product's variants: ab_product. out_of_stock_matches counts sold-out matches when none is in stock.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 1.
sortNoOrder of the listing. 'default' puts in-stock items first (relevance for a search).default
limitNoProducts per page.
queryYesProduct name or keyword, Persian or English, e.g. 'شامپو ضد شوره' or 'la roche posay'.
max_priceNoMaximum current price in Toman, e.g. 2000000.
min_priceNoMinimum current price in Toman, e.g. 1000000.
in_stock_onlyNoOnly items that can be ordered now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.3.0
    • removedInput schema / properties / in_stock_only / title
      Removed value: -"In Stock Only"
    • 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 / page / title
      Removed value: -"Page"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / sort / title
      Removed value: -"Sort"
    • removedInput schema / title
      Removed value: -"ab_searchArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "ab_searchDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive, so the safety profile needs no restating. The description adds genuine behavioral context beyond them: matching is broad and spans title and description (so titles must be inspected rather than trusted as exact hits), and out_of_stock_matches is only populated when nothing is in stock. A return-field caveat like that is exactly the value-add expected at this bar.

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?

Extremely dense with no filler: purpose first, then routing alternatives, then the one non-obvious return detail. Every clause carries information an agent would otherwise have to discover by trial.

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?

With no output schema, the description partly compensates by naming the returned fields per match and the out_of_stock_matches counter. Combined with 100% schema coverage across 7 parameters, an agent has enough to invoke correctly; only the full response envelope (pagination fields, result array name) is left implicit, which is a minor gap.

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 description coverage is 100% and every parameter (page, sort, limit, query, min_price, max_price, in_stock_only) is documented in-schema with units, defaults, and bounds. The description adds only the notion of keyword matching, not new parameter semantics, so the baseline 3 applies.

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+resource ('Search products by keyword') and immediately names what each match returns (price, discount, stock, rating), so the agent knows both the action and the payload shape. It is clearly separable from ab_find_cheapest, ab_browse, and ab_product, all of which are named.

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 when-to-use ('Use first for "price of X" / "do you have X"') plus three named alternatives with the exact condition that selects each: cheapest match → ab_find_cheapest, category/brand → ab_browse, one product's variants → ab_product. Routing is fully determined without opening other schemas.

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