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

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

bb_search_articles

Search Bonbama magazine articles by Persian or English keyword to find buying guides, discount explainers, and Gorgan list articles through title and URL slug matches.

Instructions

Search the Bonbama magazine (buying guides, discount explainers, best-of-Gorgan lists). query: Persian/English keyword. Matches article titles on the latest index pages and URL slugs.

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": {
      "query": "<query>"
    },
    "name": "bb_search_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations at all, the description carries the full behavioral burden, and it does disclose a genuinely important limitation: matching happens against article titles on the latest index pages and URL slugs, not full text or historical archives. That recall limitation is exactly the kind of context an agent needs before trusting a zero-result response. It does not cover permissions, rate limits, or result ordering, but the matching semantics are the more consequential disclosure 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?

Three short sentences, front-loaded with the resource and scope before the matching details. The pseudo-parameter label 'query:' mid-sentence is slightly awkward but the parenthetical content list earns its space by scoping recall.

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?

The tool is simple (two parameters, one required) and an output schema exists, so return values need no explanation. The description covers what is searched and how matching works; the only real hole is the undocumented 'limit' parameter, which is a minor gap against an otherwise complete definition.

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 compensate, and it partially does by explaining that 'query' is a Persian/English keyword matched against titles and slugs. The 'limit' parameter (default 10) is never mentioned in the description or the schema, leaving an agent to guess whether it caps results, pages, or something else.

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 pairs a specific verb ('Search') with a specific resource ('the Bonbama magazine') and enumerates the content types covered (buying guides, discount explainers, best-of-Gorgan lists), which lets an agent distinguish it from bb_search_businesses and bb_search_discounts. It stops short of naming a sibling, so differentiation is inferred from the content scope rather than stated.

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?

Usage is only implied by the content-type list: an agent can infer this is the tool for editorial/magazine content rather than business or discount records. There is no explicit when-to-use statement, no exclusion telling the agent when to prefer a sibling search tool, and no note about what to do if the keyword language is ambiguous.

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