Skip to main content
Glama

Part Guide

Full ranking for a category

get_ranking
Read-onlyIdempotent

The ranked list for one category and month: retailer bestseller positions or estimated shares, comparable movement, US price, and sources. 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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is fully covered and the description correctly does not restate it. It adds useful context about what comes back (positions or estimated shares, movement, US price, sources), though it never explains the difference between the two ranking modes or pagination/limit behavior.

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?

A single dense sentence, front-loaded with the scope and followed by the returned fields; nothing is wasted. The trailing 'Optional region' fragment feels tacked on and duplicates schema information, which keeps it short of a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 must convey return shape, and it does so only at the level of a field list. Key ambiguities remain unresolved for a 6-parameter tool: whether 'retailer bestseller positions' and 'estimated shares' are alternative result modes, whether ranking is global by default, and how limit interacts with rank ordering.

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%, with detailed per-parameter descriptions including region forms and month pattern, so the schema carries the meaning. The description only echoes 'Optional region' and 'one category and month', adding effectively nothing beyond what the schema documents. 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?

Specific resource and scope: 'the ranked list for one category and month', plus what the rows contain (retailer bestseller positions or estimated shares, price, sources). It does not distinguish itself from the sibling best_in_category, which sounds like an overlapping view of the same data, so an agent cannot fully disambiguate from the text alone.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given. The description never says whether this is for browsing a full leaderboard versus getting a single winner (best_in_category) or comparing selected products (compare_products). The only routing hint is parameter-level ('Omit for the global ranking'), which concerns region, not tool choice.

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