baneh-mcp

Overview Schema Source Related Servers Discussions Admin

Browse a category or brand

bn_browse

Read-onlyIdempotent

Browse products by category, brand, or price range, and sort by price or rating to find the cheapest or top-rated in-stock items for comparison.

Instructions

List products of a category and/or brand, optionally in a price range, sorted by price or rating.

Use after bn_categories / bn_brands to see what a section holds, e.g. the cheapest in-stock LG TVs (category='tv', brand='lg', sort='cheapest'). Give at least one of category, brand or a price bound.

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

Input Schema

Name	Required	Description	Default
`page`	No	Only for sort 'newest'.
`sort`	No	'newest' is the shop's order; the others are sorted here over all matches.	newest
`brand`	No	Slug from bn_brands, e.g. 'lg'.
`limit`	No	Max products.
`category`	No	Slug from bn_categories, e.g. 'tv' or 'air-conditioners-cooler'.
`max_price`	No	Maximum price in Toman, e.g. 20000000.
`min_price`	No	Minimum price in Toman, e.g. 5000000.
`in_stock_only`	No	Only items in stock (the rest are mostly discontinued, stale prices).

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.2.0Nov 7, 2026

changedInput schema / properties / brand / description

Previous value: -"Brand slug from bn_brands, e.g. 'lg' or 'xiaomi'."New value: +"Slug from bn_brands, e.g. 'lg'."

changedInput schema / properties / category / description

Previous value: -"Category slug from bn_categories, e.g. 'tv' or 'air-conditioners-cooler'."New value: +"Slug from bn_categories, e.g. 'tv' or 'air-conditioners-cooler'."

changedInput schema / properties / in_stock_only / description

Previous value: -"Only items in stock. Out-of-stock items are mostly discontinued, with stale prices."New value: +"Only items in stock (the rest are mostly discontinued, stale prices)."

changedInput schema / properties / limit / description

Previous value: -"Max products to return."New value: +"Max products."

changedInput schema / properties / page / description

Previous value: -"Result page of `limit`-sized pages (only for sort 'newest')."New value: +"Only for sort 'newest'."

changedInput schema / properties / sort / description

Previous value: -"Order. 'newest' is the shop's own order (latest added first); the others are sorted here over all matches."New value: +"'newest' is the shop's order; the others are sorted here over all matches."

First observedv0.1.0Oct 20, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open world), so the remaining burden is light. The description adds a real behavioral constraint that the schema cannot express — at least one of category/brand/price bound must be supplied — which prevents a blind unfiltered call. It does not mention result volume, pagination behavior, or ranking stability, which keeps it from a 5.

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?

Three short units: purpose first, then usage example, then the hard constraint. Every sentence carries information, and the required-input rule is placed last where it reads as a guardrail.

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?

Eight optional parameters with full schema coverage and no output schema still leave the agent needing to know the constraint and the intended workflow, both of which are stated. The shape of a returned product record is not described, though bn_product exists as the follow-up, so the gap is minor rather than blocking.

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%, so every parameter (including sort semantics, page limits, slug patterns, Toman units, and the in-stock default) is already documented. The description only restates the filter axes and demonstrates one sort value; it adds no syntax or format detail beyond the schema. The 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 and resource ('List products') plus the filter dimensions (category, brand, price range) and the sort options, which is far more than a restated title. It does not explicitly distinguish itself from the sibling bn_search or bn_find_cheapest, so an agent must infer the browse-vs-keyword-search boundary.

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 a clear sequencing rule ('Use after bn_categories / bn_brands') and a concrete invocation example with sort='cheapest', plus the hard requirement 'Give at least one of category, brand or a price bound.' It stops short of naming which sibling to use instead for free-text lookups or cheapest-item queries.

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

Deploy Server