Skip to main content
Glama
banimode-mcp

banimode-mcp

by sepehr071

Flash-sale deals

bm_deals
Read-onlyIdempotent

Lists today's flash-sale fashion products with time-limited discounts and remaining time. Use it to find what is on sale right now; check sizes with bm_product.

Instructions

List today's flash-sale products (deep time-limited discounts) with the time left.

Use for "what is on sale right now"; call bm_product for sizes.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (24 deals per page).
limitNoDeals returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • changedInput schema / properties / limit / description
      Previous value: -"Deals returned from the page."New value: +"Deals returned."
    • changedInput schema / properties / page / description
      Previous value: -"Page number, from 1 (24 deals per page)."New value: +"Page number (24 deals per page)."
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds useful temporal scoping ('today') and notes the return includes time remaining, but says nothing about result caps, total counts, or whether the deal set changes intraday — modest added value on top of rich annotations.

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?

Two short sentences, front-loaded with the core action and followed immediately by the routing hint. No filler, no redundancy with the schema.

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?

For a simple, safe read tool with a fully documented two-parameter schema and no output schema, the description covers what the tool returns (products plus time left) and when to reach for it. Nothing essential is missing, though a hint about pagination depth or the scope of 'today' would close the last gap.

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 100% (page and limit are documented, including the 24-per-page size), so the schema does the work. The description adds no paging or limit semantics beyond that, which is the expected baseline-3 case.

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?

States a specific verb and resource plus scope: 'List today's flash-sale products (deep time-limited discounts) with the time left.' That is far more precise than a name restatement. It only differentiates from one sibling (bm_product for sizes) and leaves the relationship to bm_browse/bm_search implicit, so it stops short of a 5.

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 an explicit trigger phrase — 'Use for what is on sale right now' — and names an alternative (bm_product) for a related need (sizes). There is no when-not-to-use guidance or note about what to call for non-flash-sale catalog browsing, so it is clear context but not full routing.

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