Skip to main content
Glama
banimode-mcp

banimode-mcp

by sepehr071

Brands

bm_brands
Read-onlyIdempotent

Find brand IDs by Persian or Latin name, or list initial brands when no name is given, then use the returned ID as brand_id.

Instructions

Find brand ids by name (Persian or Latin), or list the first brands when no name is given.

Pass the id as brand_id.

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_brands"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax brands.
queryNoBrand name part, Persian or Latin.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum brands returned."New value: +"Max brands."
    • changedInput schema / properties / query / description
      Previous value: -"Optional brand name part, Persian or Latin, e.g. 'ایکات' or 'nike'."New value: +"Brand name part, Persian or Latin."
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, non-destructive open-world lookup, so the safety profile is covered. The description adds that matching is on a name fragment in either Persian or Latin and that results are ids intended to be passed as brand_id elsewhere. It says nothing about truncation, how many 'first brands' are returned, or how limit interacts with listing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the primary behavior front-loaded and the downstream usage hint placed second. Nothing is wasted, though the fragment 'Pass the id as brand_id' could be attached to the first sentence for a tighter flow.

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 two-optional-parameter read-only lookup with full schema coverage and no output schema, the description covers the essential contract: what it matches on, what it returns (ids), and how to use the result. The only gap is the absence of any statement about result ordering or capping, which matters given the 'first brands' behavior.

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%, so both parameters (limit, query) are already documented in the schema. The description adds only that the name may be Persian or Latin, which the schema also states, so it provides no meaningful semantics beyond the structured fields. Baseline 3 applies.

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 gives a specific verb and resource: find brand ids by name, or list brands when no name is supplied. It also names the output explicitly (brand ids) and the accepted scripts (Persian or Latin). It stops short of naming the sibling tool it is not (e.g., bm_search or bm_categories), so differentiation is left implicit.

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?

The no-argument path (list the first brands) is stated, and 'Pass the id as brand_id' implies this is a resolution step in a larger workflow. However, there is no explicit guidance on when to prefer this over bm_search or bm_categories, and no note on when the id-lookup path should be used instead of a general search.

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