Skip to main content
Glama
Sign In
baneh-mcp

baneh-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List categories

bn_categories
Read-onlyIdempotent

List shop categories with slugs and product counts, ordered by product count. Use a parent slug to browse subcategories or a query to search all categories.

Instructions

List shop categories with slug and product count, biggest first.

No arguments: top-level sections. Use parent to open one, query to search all. Counts include out-of-stock products. Hundreds of SEO subcategories under 'tv' hold the same products. Slug goes to bn_browse.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bn_categories"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax categories.
queryNoName or slug contains this, e.g. 'یخچال'.
parentNoParent slug, to list its subcategories, e.g. 'home-appliances'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • changedInput schema / properties / limit / description
      Previous value: -"Max categories to return."New value: +"Max categories."
    • changedInput schema / properties / parent / description
      Previous value: -"Slug of a parent category to list its subcategories, e.g. 'home-appliances'."New value: +"Parent slug, to list its subcategories, e.g. 'home-appliances'."
    • changedInput schema / properties / query / description
      Previous value: -"Only categories whose name or slug contains this, e.g. 'یخچال' or 'tv'."New value: +"Name or slug contains this, e.g. 'یخچال'."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, but the description adds information annotations cannot: results are ordered biggest first, counts include out-of-stock products, and hundreds of near-duplicate SEO subcategories under 'tv' inflate the tree. The one gap is that it never mentions result truncation or the default page size behaviour.

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?

Front-loaded with the return shape, then argument modes, then two caveats, then the handoff. No filler sentences; the terse fragment style suits a reference-style tool and every line carries distinct information.

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?

There is no output schema, so the description must convey the return shape, and it does: slug plus product count, sorted descending. Combined with the argument modes and the duplicate-subcategory warning, an agent has everything needed to call this correctly on the first try.

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 description coverage is 100%, so a baseline 3 is the floor; the description earns more by clarifying the interaction between the parameters — `query` searches across all categories while `parent` scopes to one branch's children, and omitting both yields top-level sections, which is a scoping rule the schema does not state.

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 plus the exact payload: 'List shop categories with slug and product count, biggest first.' The resource is unambiguously distinct from the bn_brands, bn_product, and bn_search siblings, and 'slug goes to bn_browse' frames the handoff.

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?

Gives explicit mode selection: 'No arguments: top-level sections. Use `parent` to open one, `query` to search all.' This tells the agent exactly which argument produces which traversal, and it also names the downstream tool to use once a slug is in hand.

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