Skip to main content
Glama

Ask Bestie Computers

Biggest risers and fallers

trending
Read-onlyIdempotent

Products that gained or lost the most share this month, across all categories or one section (pc, peripherals, laptops).

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.
sectionNopc, peripherals or laptops

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 readOnly, idempotent, non-destructive and closed-world, so safety is fully covered. The description adds genuinely new behavioral context by defining the metric as share change and implying both a riser and a faller list over a month window. It does not explain the returned structure (two lists, ordering, tie handling), which is the remaining material gap.

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 sentence that front-loads the resource and metric and closes with the scoping options. No filler, though it is a compressed run-on rather than clearly structured clauses.

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 simple read-only, zero-required-parameter tool with full schema documentation and rich annotations, the description covers purpose, metric, time window and section scope adequately. The absence of an output schema means the two-list return shape is left implicit, which is a minor shortfall.

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 limit, month and section are already documented, and the description only echoes the section values and the month concept ('this month'). It adds no extra meaning such as how the section value interacts with the limit or whether the limit applies per riser/faller list.

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 market share in a month, with scope options across all categories or one section. An agent can tell this is a share-movement/trend tool rather than a plain ranking. It stops short of naming or contrasting any sibling such as get_ranking or best_in_category.

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 by the verb 'gained or lost' — an agent can infer this is for risers/fallers analysis, but there is no explicit statement of when to prefer this over get_ranking or compare_products, and no prerequisites or exclusions given.

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