Skip to main content
Glama
banimode-mcp

banimode-mcp

by sepehr071

Product categories

bm_categories
Read-onlyIdempotent

Find category IDs by name or browse the category tree: no arguments lists top sections, parent_id lists children, and the returned IDs feed bm_browse or bm_search.

Instructions

Find category ids by name, or walk the tree: no arguments lists the top sections, parent_id lists children.

Pass an id to bm_browse or bm_search.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax categories.
queryNoName part, e.g. 'مانتو'.
parent_idNoList children of this category id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum categories returned."New value: +"Max categories."
    • changedInput schema / properties / parent_id / description
      Previous value: -"List the children of this category id (e.g. 4 = لباس زنانه)."New value: +"List children of this category id."
    • changedInput schema / properties / query / description
      Previous value: -"Optional name part, e.g. 'مانتو' or 'کیف'."New value: +"Name part, e.g. 'مانتو'."
  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 and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral detail: the zero-argument call returns top-level sections and parent_id returns children, which is not derivable from the annotations. It does not mention the default 40-item cap or any pagination/truncation behavior.

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 short sentences, no filler. The core capability and its two modes come first, with the downstream chaining hint last, which is the right ordering for an agent skimming.

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 simple read-only, zero-required-parameter lookup tool with full schema coverage and rich annotations, this description covers the essentials of how to drive it. The remaining gap is that it never says what a category record contains (id/name) or that results are capped by limit, which matters slightly given no output schema.

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 coverage is 100%, so per-dimension baseline is 3 and the schema already documents limit, query and parent_id. The description still adds value by establishing the zero-argument default behavior and the parent_id child-walk semantics as a coherent tree model, which the field-level descriptions do not frame on their own.

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 ('Find category ids by name, or walk the tree') with both operating modes spelled out. It also positions itself relative to siblings by noting that the returned id feeds bm_browse or bm_search, so an agent can tell it is a lookup/enumeration tool rather than a search or browse tool.

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?

Gives concrete when-to-use context for each mode: no arguments for top sections, parent_id for children, and name lookup via query. It also describes the downstream workflow (pass the id to bm_browse/bm_search). It lacks explicit exclusions, e.g. when to prefer bm_search over a name query here.

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