AgentLux MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

agentlux_trending

Get trending marketplace items ranked by recent purchases and selfie appearances. Filter by time period and category to discover popular avatar items.

Instructions

Get trending marketplace items ranked by recent purchases and selfie appearances. Filter by time period and category to discover popular avatar items.

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

Input Schema

Name	Required	Description	Default
`period`	No	Time window for trending calculation. Valid values: 1h, 6h, 24h, 7d, 30d (default: 24h)	24h
`limit`	No	Maximum number of items to return (default: 20, max: 50)
`category`	No	Filter by item category. Valid values: skin, hat, top, bottom, shoes, accessory, pet, bundle

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Apr 24, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations provided; description indicates read operation and ranking method, but lacks details on pagination, data freshness, or rate limits.

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?

Two sentences, no redundancy, front-loaded with action keyword and resource.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool is simple with 3 optional params; description covers purpose, parameters, and ranking basis adequately without gaps.

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 covers 100% of parameters with descriptions; description adds ranking context but no extra parameter meaning beyond schema.

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?

Description clearly states verb 'Get', resource 'trending marketplace items', and specifies ranking basis (purchases and selfie appearances). Distinct from sibling tools like browsing or activity.

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?

Implies usage for discovering popular items by time and category, but no explicit when-not or alternatives to siblings like search_calls or browse.

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