Skip to main content
Glama

Zoya.bg

list_bestsellers

Show up to ten Zoya.bg bestsellers in storefront order. Omit category for the official store bestseller selection. For a specific category use a name from session_start.bestsellers.categories. Show the Zoya cards once. Photos appear only in those cards: any list you write yourself is text only (name linked to product_url, package size, price), with no images or image placeholders, and never search for product images by name.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses important display behavior: up to ten results, storefront order, Zoya cards shown once, and text-only user-written lists with no images or image placeholders. It does not state read-only semantics or permissions, but it gives substantial behavioral context for a display/list tool.

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?

The purpose is front-loaded and the sentences are generally efficient. The final display constraints are somewhat dense but each rule appears relevant to correct invocation, with no obvious filler.

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 low-complexity list tool with no output schema, the description adequately covers result scope, category selection, and output presentation constraints. The main gap is precise limit parameter behavior, plus no explicit read-only or permission context.

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 explain both parameters. It explains the category parameter's source and omission behavior, and "up to ten" implies a cap related to limit, but it does not clearly explain that the limit parameter controls result count or what values are valid.

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 states a specific verb and resource: "Show up to ten Zoya.bg bestsellers in storefront order." It is clear what the tool does, but it does not explicitly distinguish itself from sibling listing tools such as list_new_products.

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?

It gives concrete when-to guidance for the category parameter: omit it for the official bestseller selection, or provide a category name from session_start.bestsellers.categories. It does not explicitly exclude other tools or explain when not to use this one, but the category alternatives are clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources