Skip to main content
Glama

Biggest risers and fallers

trending
Read-onlyIdempotent

Products that gained or lost the most share this month, across all categories or one section (face, eyes, lips, skin).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "trending"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPer list (default 5)
monthNoMonth as YYYY-MM. Defaults to the latest month.
sectionNoface, eyes, lips or skin

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so safety is covered. The description adds that results are scoped to a single month and to either all categories or one section, but it never clarifies that risers and fallers are returned as separate lists, which the schema's 'Per list' wording hints at.

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?

One sentence, front-loaded with the resource and metric, followed by the scope and the enumerated section values. Nothing is wasted and nothing is buried.

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 would need to say what comes back, and it never states that there are two ranked lists or how the share metric is expressed. For a three-parameter, zero-required analytics tool it is adequate but leaves the return shape underspecified.

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 limit, month, and section. The description adds a modest amount: that omitting section means all categories and that the scope is monthly, which is the baseline expected when the schema does the heavy lifting.

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 names a specific resource and metric (products that gained or lost the most share) plus a time scope (this month), which is far more informative than the title alone. It does not explicitly distinguish itself from siblings like get_ranking or best_in_category, so it stops short of a 5.

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 phrasing: use this for month-over-month share movement, either across all categories or narrowed to one section. There is no explicit statement of when to prefer get_ranking or best_in_category instead, so the agent must infer the boundary.

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