Skip to main content
Glama

Part Guide

Best / most popular product in a category

best_in_category
Read-onlyIdempotent

Answers "what is the best / most popular / most used X". Returns a one-sentence answer, the #1 and #2, the cheapest product in the top five, the fastest riser, the top 10, the sources the estimate is based on and the page URL. Measures and sources are stated in each answer. Optional region, brand ("AMD", "Intel", "NVIDIA"), os ("macOS", "Windows") and budget_usd.

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": {
      "category": "<category>"
    },
    "name": "best_in_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
osNoLaptops only: macOS or Windows
brandNoOnly this brand, e.g. AMD
monthNoMonth as YYYY-MM. Defaults to the latest month.
regionNoOptional region: a code (US, CA, UK, EU, SE, NO, DK, AU), a market (na, eu, uk, nordics, au) or a name like "Sweden". Omit for the global ranking.
categoryYesCategory in plain words, e.g. "gaming mouse", "CPU", "graphics card", "laptop for video editing", or an id from list_categories.
budget_usdNoAlso return the most picked product at or under this US price

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds real payload detail: a one-sentence answer, #1 and #2, cheapest in top five, fastest riser, top 10, underlying sources and page URL, with measures/sources stated per answer. It stops short of stating anything about data freshness or estimation error, which matters for a rankings 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?

Front-loaded with the question it answers, then a compact enumeration of the return payload, then the optional filters. The return-field list is long but each item is informative; no filler sentences.

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?

With no output schema, the description carries the return-shape burden and does so thoroughly, and the six parameters are fully covered by schema descriptions. The only real gap is absent guidance on choosing this over ranking/comparison siblings.

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 coverage is 100%, so the schema already documents region codes, brand, os, month format and budget semantics. The description only re-summarizes the optional filters with a couple of examples and actually omits month entirely, so it adds little beyond the schema.

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?

Opens with the exact question shape it answers ("what is the best / most popular / most used X"), a specific verb-equivalent and resource, and enumerates what comes back. It is clearly distinct from get_product or compare_products, though it never names a sibling to route against.

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

Usage Guidelines3/5

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

Usage is implied by the question pattern rather than stated: an agent can infer this is for "best/most popular" queries, but there is no explicit when-not-to-use or pointer to get_ranking or compare_products for adjacent needs.

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