Skip to main content
Glama
baneh-mcp

baneh-mcp

by sepehr071

Get product details

bn_product
Read-onlyIdempotent

Retrieve a product's price in Toman, stock status, rating, brand, categories, specs, highlights, description, and images by product ID; variations list options only.

Instructions

Get one product: price (Toman), stock, rating, brand, categories, spec attributes, highlights, description, images.

Variations list options only (no per-variation price or stock). Next: bn_reviews.

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": {
      "product_id": "<product_id>"
    },
    "name": "bn_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYesProduct id from a search or browse, e.g. 69045.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / product_id / description
      Previous value: -"Product id from bn_search, bn_find_cheapest or bn_browse, e.g. 69045."New value: +"Product id from a search or browse, e.g. 69045."
  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 readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description still adds real value beyond them by stating the price currency (Toman) and warning that the variations list carries options only, with no per-variation price or stock — a data-shape caveat that prevents wrong assumptions.

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 compact blocks, front-loaded with the resource and its returned fields, followed by the variations caveat and a next-step pointer. Every sentence carries information and nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly takes on the job of enumerating returned fields, so an agent knows what to expect from the call. It also covers the one surprise an agent could hit (variations lacking price/stock) and points to the logical next tool.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains the format and origin of product_id (including an example). The description adds no further meaning about the parameter, which is acceptable given the schema does the work.

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?

The description opens with a specific verb and resource ("Get one product") and enumerates exactly what the single record contains: price in Toman, stock, rating, brand, categories, spec attributes, highlights, description, images. That distinguishes it implicitly from bn_search and bn_browse as the single-record detail lookup, though it never names those siblings by contrast.

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?

Usage is only implied: the tool fetches details for one product, and "Next: bn_reviews" supplies a forward workflow step. There is no explicit statement of when to prefer this over bn_search or bn_browse, and the guidance that product_id comes "from a search or browse" lives in the schema rather than the description.

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