Skip to main content
Glama
io.github.mohammad-abbasi-sh/bonbama-mcp

io.github.mohammad-abbasi-sh/bonbama-mcp

bb_search_businesses

Search Bonbama businesses by Persian or English keyword or category slug to get names, URLs, slugs, and active campaign counts for local deal research.

Instructions

Search Bonbama businesses by keyword and/or category.

query: Persian/English keyword (e.g. "ناخن", "testino"). category: a category slug from bb_list_categories (e.g. "zban", "rstoran"). Give at least one of query/category. Returns name, URL, slug and active-campaign count per business.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
categoryNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; 'Search' implies a read-only, non-destructive operation and it does disclose the returned fields (name, URL, slug, active-campaign count). However, it says nothing about result limits, ordering, or pagination behavior, which are the main operational unknowns here.

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?

The purpose is front-loaded in the first sentence and the per-parameter notes follow in a compact, scannable order. The inline examples are useful rather than padding, though the paragraph is denser than it needs to be for three parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description need not explain return values, and it briefly does anyway. But with 0% schema coverage and no annotations, leaving `limit` (and any paging behavior) undocumented leaves an agent guessing on result-size control, which is a meaningful hole for a search tool.

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 0%, so the description must compensate, and it does well for two of three params: query is documented as Persian or English with examples, category as a slug sourced from bb_list_categories with examples, and the at-least-one constraint is stated explicitly. The `limit` parameter is never mentioned, which is the remaining gap.

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 states a specific verb (search) and resource (businesses) plus the two facets it searches on, so it is distinguishable from bb_search_articles and bb_search_discounts by resource. It does not explicitly contrast with bb_get_business, but the scope is unambiguous without that.

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?

It gives a concrete operating rule — 'Give at least one of query/category' — and tells the agent where category slugs come from (bb_list_categories), which is a real prerequisite for correct invocation. It lacks explicit when-not guidance, but the usage context is clear.

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