Skip to main content
Glama
Sign In
baneh-mcp

baneh-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Search products

bn_search
Read-onlyIdempotent

Search Baneh products by name in Persian or English and filter by price, stock, and rating to compare in-stock items.

Instructions

Search Baneh products by name in Persian or English, with price (Toman), stock and rating.

A multi-word query must appear as a phrase in the title; for the lowest price use bn_find_cheapest. Next: bn_product.

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_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOnly for sort 'newest'.
sortNo'newest' is the shop's order; the others are sorted here over all matches.newest
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. Changed5 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 / page / description
      Previous value: -"Result page of `limit`-sized pages (only for sort 'newest')."New value: +"Only for sort 'newest'."
    • 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'."
    • 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."
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world behavior, so the description's real contribution is the non-obvious matching rule: a multi-word query must appear as a phrase in the title, which materially affects how an agent phrases queries. It doesn't discuss result-set breadth, pagination, or the default in-stock filtering, but the phrase rule is substantive added context beyond annotations.

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?

Two compact sentences with the core purpose front-loaded and the routing hints after. The 'Next: bn_product' line is terse but earns its place as workflow guidance; nothing is 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 seven-parameter search with no output schema, the description covers purpose, result fields, matching semantics, and the key alternative. Remaining gaps (pagination behavior, how filters combine with sort) are largely handled by the schema.

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 coverage is 100%, so all seven parameters are already documented, and the description only echoes the Persian/English and Toman facts already in the schema. It adds no meaning about sort, page, or price-range interaction beyond what the schema states, 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 and resource ('Search Baneh products by name') and names the result fields (price in Toman, stock, rating), which is more than a restatement of the name. It distinguishes itself from bn_find_cheapest, though it does not differentiate from bn_browse, the other listing-style sibling.

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?

Explicitly routes the 'lowest price' use case to bn_find_cheapest and points to bn_product as the follow-up, which is clear alternative guidance. It lacks an explicit when-not relative to bn_browse, so coverage is not complete.

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