Skip to main content
Glama

Ask Bestie Computers

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. Shares are estimated % of builds/purchases. 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.9/5.0
Behavior5/5

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

Annotations already declare this is a safe read-only, idempotent, non-destructive call, and the description goes well beyond them by enumerating the return payload (one-sentence answer, #1 and #2, cheapest in the top five, fastest riser, top 10, sources, page URL) and defining what a share actually measures (estimated % of builds/purchases). That is exactly the behavioral context needed since no output schema exists.

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 core purpose is front-loaded in the first clause and the payload list follows as compact enumeration with no filler sentences. The second sentence is dense (a long comma list of returned items) but every element conveys a distinct return value.

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 read-only query tool with no output schema, the description covers purpose, filters, and return shape thoroughly, and annotations cover the safety profile. Minor gaps remain: it does not say what happens with an ambiguous or unrecognized category, or whether an empty result is possible.

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 all six parameters are already documented, and the description adds only illustrative examples (brand "AMD"/"Intel"/"NVIDIA", os "macOS"/"Windows"). It clarifies that omitting region yields the global ranking, but the schema already states that, so the marginal value is modest and the baseline 3 applies.

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 opens with a direct restatement of the question it answers ("what is the best / most popular / most used X") plus the resource being ranked, so an agent can immediately tell this is an answer-style ranking tool rather than a raw data fetch. It does not explicitly distinguish itself from siblings like get_ranking or trending, which keeps it out of the 5 band.

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 quoted phrasings ("best", "most popular", "most used") and by the optional filters listed at the end, but there is no statement of when to prefer this over get_ranking or trending, nor any exclusion or precondition. An agent must infer the selection rule from the question phrasing.

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