Skip to main content
Glama
banimode-mcp

banimode-mcp

by sepehr071

Product details

bm_product
Read-onlyIdempotent

Retrieve a single product's color prices, discounts, per-size stock, features, and short description; use after search or deals to verify availability and Toman prices.

Instructions

Get one product: every color with its price, discount, stock per size, features and short description.

Use after bm_search or bm_deals to check size stock and color prices (Toman).

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

Input Schema

NameRequiredDescriptionDefault
product_idYesProduct id from search results.

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 (the `id` in search results), e.g. 271079."New value: +"Product id from search results."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds value beyond them by disclosing the shape of the payload (per-color pricing, per-size stock, features, description) and the currency unit (Toman). It does not cover behavior for an invalid or missing product_id, which keeps it below 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?

Two sentences, both front-loaded with the highest-value information: what is returned first, then when to call it. No filler, no repetition of the title.

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 carries the burden of describing return values and does so concretely (colors, prices, discounts, size-level stock, features, description). For a one-parameter read tool this is complete enough for an agent to call it correctly.

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% and the single parameter is documented as "Product id from search results," which matches the description's usage hint. The description adds no new syntax, format, or constraint information about product_id, so the baseline 3 applies.

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?

States a specific verb and resource ("Get one product") and enumerates exactly what comes back: per-color price, discount, stock per size, features, short description. That single-item, full-detail scope is clearly distinct from the list-oriented siblings (bm_search, bm_deals, bm_browse).

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 positions the tool in a workflow: "Use after bm_search or bm_deals to check size stock and color prices," naming the upstream siblings and the agent's goal. It lacks an explicit when-not-to-use clause or a statement that this is not for listing/discovery, so it falls just short of a 5.

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