1845 Smoked Meat AI Gateway

Best sellers

best_sellers

Read-onlyIdempotent

The store's best-selling / most popular products, ranked by real units sold from captured orders. Use this to answer "what is your best product", "most popular", "top seller", or to recommend what to buy.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No	Look-back window in days (default 90, max 365)
`limit`	No	How many products to return (default 10, max 25)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`window_days`	No
`best_sellers`	Yes

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable behavioral context by clarifying that ranking is based on real units sold from captured orders, which prevents the agent from treating 'most popular' as a subjective or review-based measure.

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?

The description is a single sentence that front-loads the core purpose, adds the key ranking detail, and gives concrete usage examples. Every part earns its place and there is no redundant filler.

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?

With a full output schema, clear annotations, and only two optional self-explanatory parameters, the description covers everything an agent needs to select and invoke the tool correctly. The ranking basis and example queries remove ambiguity.

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%, so the schema already documents days and limit with defaults and max values. The description adds no new parameter detail, which is acceptable given the strong schema coverage.

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?

The description clearly identifies the resource (best-selling products), the ranking criterion (real units sold from captured orders), and the intended queries. It differentiates from siblings like related_products and search_products by focusing on aggregate sales popularity rather than relevance or relatedness.

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 description explicitly states when to use it: for 'what is your best product', 'most popular', 'top seller', or purchase recommendations. It doesn't explicitly list exclusions or alternatives, but the use cases are concrete enough to guide an agent.

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

All 1845 Smoked Meat AI Gateway tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Most tools target distinct actions: browse, search, product detail, inventory, recommendations, cart, and store policy. The main potential confusion is between get_product and check_inventory, which both report product/variant price and stock, though list_products vs search_products is reasonably clear from descriptions.

Naming Consistency3/5

Tool names are consistently snake_case and many follow a verb_noun pattern like check_inventory, get_product, list_products, and search_products. However, best_sellers, related_products, and store_info are noun phrases, while fetch and search are bare verbs, making the naming pattern mixed but still readable.

Tool Count5/5

Eleven tools is well-scoped for an e-commerce shopping assistant covering catalog browsing, product search, inventory checks, recommendations, cart assembly, content search, and store policies. Each tool has a clear purpose and the count is neither bloated nor too thin.

Completeness5/5

The tool set covers the full shopper-facing journey: discovering categories and products, searching content, viewing product details and stock, seeing best sellers and related items, checking store policies, and building a cart. As a read-only storefront gateway, missing merchant-side operations are outside its stated purpose.

Resources

Need Help?