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

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

bb_search_discounts

Search active discount campaigns site-wide by keyword, or list popular campaigns when no query is given. Returns business, title, discount, Jalali expiry, campaign URL, and sent-code count.

Instructions

Search ACTIVE discount campaigns site-wide by keyword (e.g. "کفش", "شهربازی"). With no query, returns current popular campaigns. Each result: business, campaign title, discount, Jalali expiry, campaign URL and how many codes were sent.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations present, the description carries the disclosure burden and does well: it reveals the implicit ACTIVE-only filter and the default behavior when no query is supplied. It does not cover auth requirements, pagination, or how large limit may go, which leaves some behavioral gaps.

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?

Three short sentences, front-loaded with the core action and the default behavior. The final sentence enumerating result fields mostly restates what the output schema already exposes, so it earns only partial credit.

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?

For a two-parameter, zero-required read tool with an output schema, the description covers scope, default behavior, and the active-only constraint. The only omission is the meaning of limit, which is minor given everything else is supplied.

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 0%, so the description must supply parameter meaning. It explains query well (keyword, example values, empty means popular campaigns) but says nothing about limit, leaving one of two parameters completely undocumented.

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 (search) and a narrowly scoped resource (ACTIVE discount campaigns, site-wide, by keyword), including example queries in Persian. It is unmistakable against siblings like bb_search_articles or bb_search_businesses, which target entirely different resources.

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 explicit operating context: the search only covers active campaigns, and omitting the query returns currently popular campaigns. That tells the agent how to use the empty-query path, but it names no alternative tool or exclusion conditions for when this is the wrong choice.

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