Skip to main content
Glama
banimode-mcp

banimode-mcp

by sepehr071

Browse a category or brand

bm_browse
Read-onlyIdempotent

Lists Banimode products by category and/or brand using filters for price, size, stock, and sort, so you can browse a catalog and compare matching fashion items.

Instructions

List the products of a category and/or brand, with the same filters and cards as bm_search.

Give category_id or brand_id (at least one).

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": "bm_browse"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number.
sizeNoSize label, e.g. 'M', '42', 'فری سایز'.
sortNo'discount' = biggest saving first.relevance
limitNoProducts per page.
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. Changed9 schema fields changedv0.2.0
    • changedInput schema / properties / brand_id / description
      Previous value: -"Brand id from bm_brands, e.g. 4124 (ایکات)."New value: +"Brand id from bm_brands."
    • changedInput schema / properties / category_id / description
      Previous value: -"Category id from bm_categories, e.g. 668 (مانتو)."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 / 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.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds that results carry 'the same filters and cards as bm_search', which conveys the return shape and filter parity. It says nothing about pagination behavior or how results are ordered beyond the schema's sort enum.

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 what the tool returns before the invocation constraint. Nothing is redundant or padded.

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 9-parameter listing tool with no output schema, the description covers what is returned ('cards as bm_search') and the one hard invocation rule. It leaves the agent to infer result ordering and pagination from the schema, and assumes familiarity with bm_search's card format, which is a minor gap.

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 a cross-parameter constraint that the schema cannot express: every field is nullable and nothing is required, yet at least one of category_id/brand_id must be supplied. That is meaningful semantics beyond the input schema for a 9-parameter tool.

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 the products') and scopes it to 'a category and/or brand', which separates it from the free-text bm_search. The reference to bm_search also signals the shared result shape. It stops short of explicitly contrasting itself with bm_deals or bm_categories, so the sibling differentiation is implied rather than stated.

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?

'Give category_id or brand_id (at least one)' is a genuine precondition that tells the agent how to invoke it validly. However, there is no explicit when-to-use/best-alternative guidance — an agent with a text query is left to infer that bm_search is the right sibling, and nothing says when bm_browse is the wrong choice.

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