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

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

bb_health

Check whether bonbama.ir is reachable right now and get its current status — ok, blocked by a bot wall or rate limit, or error — along with the HTTP status code and probed URL.

Instructions

Check whether bonbama.ir is reachable right now.

Returns status ok (HTTP 200), blocked (HTTP 403/429 — bot wall or rate limit) or error, plus the HTTP status and the probed URL. One polite request; it does not fetch any listings.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it enumerates the three outcome states (ok/blocked/error), explains what blocked means (403/429 bot wall or rate limit), and discloses the behavioral footprint ('one polite request; it does not fetch any listings'). It omits whether authentication is needed and how timeouts are classified, keeping it from a 5.

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

Conciseness5/5

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

Three short lines, front-loaded with the core question, then the return states, then the side-effect constraint. Every sentence adds information an agent would otherwise have to guess.

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 zero-parameter health probe with an output schema present, the description covers everything an agent needs: what it checks, the possible statuses, what each status means, and that it performs only one non-data-fetching request.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly adds no pseudo-parameter guidance and stays focused on outcomes.

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 and resource: 'Check whether bonbama.ir is reachable right now.' Combined with the name bb_health, an agent knows instantly this is an availability probe, not a data-fetch tool, which cleanly separates it from every bb_search_* sibling.

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 line 'it does not fetch any listings' implicitly frames this as a pre-flight/probe tool rather than a search substitute, and 'right now' signals a live availability check. There is no explicit 'use this before X' or exclusion statement, so it stops short of a full when/when-not directive.

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