Skip to main content
Glama

Ask Bestie Computers

Full ranking for a category

get_ranking
Read-onlyIdempotent

The ranked list for one category and month: estimated share of builds/purchases, change in percentage points vs the previous month, rank last month, US price, and the sources behind it. Optional region.

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

Input Schema

NameRequiredDescriptionDefault
osNoLaptops only: macOS or Windows
brandNoOnly this brand
limitNoMax products (default 10)
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.

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 declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered. The description adds real value beyond that by disclosing what data is returned and that the figures are estimates with 'the sources behind it' — provenance information an agent would otherwise have to guess at. It still says nothing about the limit/pagination behavior beyond the schema.

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?

Two compact sentences, front-loaded with the core resource and then the payload fields; no filler. The trailing 'Optional region' fragment is terse and slightly modal but does carry information.

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 does the work of enumerating return fields, which is the key gap it needed to fill. Combined with fully documented parameters and read-only annotations, an agent has enough to call it correctly; only result shape (list of product entries) and limit interaction are left implicit.

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 with examples and defaults. The description only restates the category/month scope and flags region as optional, adding no syntax or interpretation the schema lacks. 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?

States a specific resource and scope: 'the ranked list for one category and month,' then enumerates the returned fields (share of builds/purchases, pp change, prior rank, US price, sources). An agent knows exactly what it retrieves, though it never names or contrasts with the sibling best_in_category, which sounds closely related.

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 only implied: the description frames the tool as the full ranked list for a single category-month, and 'Optional region' hints that omitting it yields the global view. There is no statement of when to prefer this over best_in_category, trending, or get_product, and no exclusions.

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