Skip to main content
Glama
Sign In
Rally MCP Server

Rally MCP Server

by andrehocsis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

trending_products

Get trending products on Mercado Libre and Shopee by category. Ranks top items by sales velocity and includes commission estimates.

Instructions

Get trending products on Mercado Libre or Shopee by category. Returns top products ranked by sales velocity with commission estimates.

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": {
      "marketplace": "<marketplace>"
    },
    "name": "trending_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketplaceYes
categoryNoCategory ID
periodNo7d

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It explains the output includes top products by sales velocity and commission estimates, but does not mention any side effects, authentication needs, or rate limits. The tool appears to be read-only, but this is not explicitly stated.

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?

The description is a single sentence that conveys all essential information without any redundancies. It is efficiently structured and front-loaded.

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?

Given the tool's simplicity (3 required parameters, no output schema, no nested objects), the description provides sufficient context on what it returns (top products by sales velocity with commission estimates). However, it could be improved by listing example return fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, with only 'category' having a description ('Category ID'). The description adds 'by category' but does not explain the marketplace enum, period values, or default behavior. The low coverage is not adequately compensated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool is for getting trending products from Mercado Libre or Shopee by category, with ranking by sales velocity and commission estimates. It is distinct from sibling tools like search_products or analyze_product.

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?

The description implies usage for retrieving trending products but does not explicitly state when to use versus alternatives or provide any exclusion criteria. Lacks guidance on when not to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools