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

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

bb_get_business

Retrieve full details for a single bonbama.ir business using its slug, including rating, address, category, active discount campaigns, expiry dates, and published discount codes.

Instructions

Full details for one business: name, description, city, address, rating, category, ACTIVE campaigns (title, discount, expiry — read live from the page) and any literal discount codes published on the page. slug: e.g. "testino", "takchh" (from bb_search_businesses).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "bb_get_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose a meaningful trait by noting campaigns are 'read live from the page', which signals freshness and possible latency/variability. It says nothing about behavior for an unknown slug (error vs empty), whether inactive campaigns are excluded, or any auth/rate-limit constraints.

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 sentences, front-loaded with the resource and its payload. The field enumeration is dense but each item is useful for deciding whether this tool answers a given need; minor tightness could be gained from grouping the campaign sub-fields.

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?

An output schema exists, so the return shape need not be explained, and the description still previews the key content. What is missing is edge-case behavior (invalid slug, business not found) and any note on whether campaign data is cached or live-only, which matters given the 'read live' claim.

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 0% for the single slug parameter, but the description compensates by defining it as a page slug with concrete examples ('testino', 'takchh') and naming the tool that produces it. That is materially more than the bare {type: string} schema offers.

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?

Opens with a specific verb and a precise scope: 'Full details for one business', then enumerates the exact fields returned (name, description, city, address, rating, category, campaigns, discount codes). That distinguishes it from the sibling search tools, which return collections rather than one record.

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?

The parenthetical '(from bb_search_businesses)' tells the agent where the slug comes from and implies this is the follow-up call after a search. It stops short of an explicit when-not-to-use statement (e.g. 'do not call for browsing; use bb_search_discounts for code-only lookups').

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