Skip to main content
Glama
banimode-mcp

banimode-mcp

by sepehr071

Search products

bm_search
Read-onlyIdempotent

Search Banimode’s fashion catalog by keyword to find priced products with discounts, colors, and in-stock sizes; filter by price, brand, category, or sort results.

Instructions

Search Banimode fashion products by keyword and return priced cards with discount, color and sizes in stock.

Each card is one product in one color (ids repeat). Call bm_product for all colors and sizes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "bm_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number.
sizeNoSize label, e.g. 'M', '42', 'فری سایز'.
sortNo'discount' = biggest saving first.relevance
limitNoProducts per page.
queryYesSearch words, Persian works best, e.g. 'مانتو مجلسی'.
brand_idNoBrand id from bm_brands.
in_stockNoOnly products with stock.
max_priceNoMaximum price, Toman.
min_priceNoMinimum price, Toman.
category_idNoCategory id from bm_categories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.2.0
    • changedInput schema / properties / brand_id / description
      Previous value: -"Optional brand id from bm_brands to narrow the search."New value: +"Brand id from bm_brands."
    • changedInput schema / properties / category_id / description
      Previous value: -"Optional category id from bm_categories to narrow the search."New value: +"Category id from bm_categories."
    • changedInput schema / properties / in_stock / description
      Previous value: -"Only products with stock (default true). Sold-out items clutter price sorts."New value: +"Only products with stock."
    • changedInput schema / properties / limit / description
      Previous value: -"Products per page (about 0.4 KB each)."New value: +"Products per page."
    • changedInput schema / properties / max_price / description
      Previous value: -"Maximum price in Toman, e.g. 2000000."New value: +"Maximum price, Toman."
    • changedInput schema / properties / min_price / description
      Previous value: -"Minimum price in Toman, e.g. 500000."New value: +"Minimum price, Toman."
    • changedInput schema / properties / page / description
      Previous value: -"Page number, from 1 (the site caps results at 10000)."New value: +"Page number."
    • changedInput schema / properties / query / description
      Previous value: -"Search words, Persian works best, e.g. 'مانتو مجلسی' or 'کفش اسپرت مردانه'."New value: +"Search words, Persian works best, e.g. 'مانتو مجلسی'."
    • changedInput schema / properties / size / description
      Previous value: -"One size label to require, e.g. 'M', 'XL', '42', 'فری سایز'."New value: +"Size label, e.g. 'M', '42', 'فری سایز'."
    • changedInput schema / properties / sort / description
      Previous value: -"'relevance' (default), 'cheapest', 'expensive', 'discount' (biggest saving first), 'newest'."New value: +"'discount' = biggest saving first."
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds behavior the annotations cannot: results are per-product-per-color cards with duplicate ids, and it explains why (one card per color), which directly prevents an agent from misreading a repeated id as a duplicate result. Return format limits (paging, totals) are not covered.

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?

Two short sentences, front-loaded with purpose and return shape, then the critical caveat about repeated ids and the follow-up tool. Every sentence carries information; nothing is redundant or buried.

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 ten parameters and no output schema, the description correctly takes on the job of explaining the response shape (cards, discount, color, sizes) and the id-repetition quirk. Small gaps remain around pagination semantics (page/limit defaults and max) and whether totals are returned, but nothing needed to invoke the tool 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 description coverage is 100% and each of the ten parameters is documented in the schema, including enum meaning for sort, units for price bounds, and cross-tool references for brand_id/category_id. The description adds no parameter-level detail beyond the implicit 'keyword search' and 'in stock' notions, so baseline 3 applies.

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 (search) and resource (Banimode fashion products), and describes the return shape (priced cards with discount, color, sizes). It differentiates itself from bm_product by telling the agent to go there for all colors/sizes, but it never distinguishes itself from keyword-adjacent siblings like bm_browse or bm_deals.

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

Usage Guidelines3/5

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

The line 'Call bm_product for all colors and sizes' gives one explicit alternative and the condition that selects it, which is genuine routing guidance. However, there is no guidance on when to use search instead of browse/deals/categories, nor on paging through results, so usage is mostly implied by the name.

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