Skip to main content
Glama
Sign In
BOS MCP Server

BOS MCP Server

by bizino
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

bos_smart_top_products

Retrieves top products ranked by revenue or quantity sold, with detailed variant performance data for a specified date range.

Instructions

Lấy top N sản phẩm theo doanh thu, số lượng bán, bao gồm chi tiết hiệu suất từng phân loại (variant).

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": {
      "limit": "<limit>",
      "sort_by": "<sort_by>",
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "bos_smart_top_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitYesSố lượng sản phẩm cần lấy (mặc định 10)
sort_byYesSắp xếp theo doanh thu hoặc số lượng
start_dateYesNgày bắt đầu (YYYY-MM-DD)
end_dateYesNgày kết thúc (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided. Description does not disclose whether the tool is read-only, what permissions are needed, performance characteristics, or potential side effects. For a data retrieval tool, basic behavioral transparency is lacking.

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?

Single sentence efficiently conveys purpose, resource, scope, and output characteristics. No wasted words; every part earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description should elaborate on return structure (e.g., fields, pagination). It mentions variant performance but not specific data points. With 4 required parameters and no output schema, more detail would be beneficial.

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 100% with parameter descriptions. Description adds value by clarifying that results include 'chi tiết hiệu suất từng phân loại (variant)', which goes beyond schema definitions.

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?

Description clearly states it retrieves top N products by revenue/quantity with variant performance details. Verb 'Lấy' (get) and resource 'sản phẩm' are specific, distinguishing it from sibling tools like 'bos_product_list' or 'bos_product_search'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives (e.g., 'bos_product_list' for simple listing, or other smart tools). No mention of prerequisites or time-based constraints implied by required date parameters.

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

Deploy Server

Other Tools