Skip to main content
Glama
Sign In
baneh-mcp

baneh-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Find cheapest product

bn_find_cheapest
Read-onlyIdempotent

Find products matching all query words, sorted by price in Toman, with min/max price and in-stock filters to identify lower-cost options.

Instructions

Find the cheapest products whose title contains every word of the query, one list sorted by price (Toman).

Use for the lowest price of X. Words may come in any order. Raise min_price to skip accessories and spare parts. Unpriced items are skipped. complete=false means more matches than the 2,000 scanned. The same title can be a different model or size.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax products.
queryYesProduct name or keyword, Persian or English, e.g. 'iphone'.
max_priceNoMaximum price in Toman, e.g. 20000000.
min_priceNoMinimum price in Toman, e.g. 5000000.
in_stock_onlyNoOnly items in stock (the rest are mostly discontinued, stale prices).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • 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 / query / description
      Previous value: -"Product name or keyword, Persian or English, e.g. 'تلویزیون ال جی 55' or 'iphone'."New value: +"Product name or keyword, Persian or English, e.g. 'iphone'."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses matching behavior (all words, any order), sort order and currency, skipping unpriced items, a 2,000-item scan cap surfaced via complete=false, and the important caveat that identical titles may be different models or sizes. These are substantive behavioral details that annotations alone do not provide.

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 description is short and front-loaded, leading with the core purpose before caveats. Some phrasing is clipped or awkward, such as 'one list sorted by price (Toman)' and the standalone 'complete=false' sentence, but nothing is redundant.

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 read-only search tool with a fully documented schema and clear annotations, this is close to complete: matching rules, sorting, scan limits, and a data-quality caveat are all covered. It does not describe the returned product fields, which is a minor gap given there is no output schema.

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. The description still adds useful meaning: it explains the word-matching semantics of query, the rationale for min_price (skipping accessories and spare parts), and reiterates price units in Toman.

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?

The description states a specific verb and resource ('Find the cheapest products') and defines the matching scope ('whose title contains every word of the query'), sorted by price. This clearly distinguishes it from the broader bn_search sibling by its cheapest-price specialization.

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?

It gives a direct when-to-use rule ('Use for the lowest price of X') and a practical hint to raise min_price for accessories. It does not explicitly name bn_search as the alternative for non-price-ranked searches, so routing guidance is clear but not exhaustive.

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