Skip to main content
Glama
sepehr071

asalbanoo-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Product details

ab_product
Read-onlyIdempotent

Fetch complete details for one chosen Asal Banoo product after search or browse: price/discount in Toman, stock, every size/color variant, brand, rating, images, and key facts.

Instructions

Get one product: price/discount (Toman), stock (exact count when low), every size/color variant with its own price and stock, brand, categories, rating, key facts (volume, expiry, skin/hair type, origin), image(s).

Use after ab_search / ab_browse when the user picks a product. Reviews: ab_reviews.

Input Schema

NameRequiredDescriptionDefault
product_idYesAsal Banoo product id from ab_search / ab_browse, e.g. 6963.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.0
    • removedInput schema / properties / product_id / title
      Removed value: -"Product Id"
    • removedInput schema / title
      Removed value: -"ab_productArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "ab_productDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered. The description adds useful value by disclosing return detail, notably 'exact count when low' for stock, which is a non-obvious behavior. It doesn't discuss failure modes (e.g., invalid product_id) or formatting, but is strong enough.

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 tight sentences: first front-loads the returned fields, second gives usage context and the review alternative. No filler.

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?

A read-only, single-parameter lookup documented rich enough for an agent to call correctly; return fields are enumerated though no output schema exists. Minor gap: no mention of behaviour when the id doesn't exist, but the core is complete.

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%: product_id is fully documented with source, type, range, and example. The description adds no parameter syntax details beyond referencing where to obtain the id, so baseline 3 is appropriate.

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+resource ('Get one product') and then enumerates precisely what is returned (price/discount, stock, variants, brand, rating, facts, images). Clearly distinguished from siblings, which are search/browse/review tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use it ('after ab_search / ab_browse when the user picks a product') and routes related needs to a named sibling ('Reviews: ab_reviews'). This is a complete when-to-use and alternative routing.

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