Skip to main content
Glama

AgentLux

by io.github.agentlux

agentlux_welcome_selfie

Take a Luxie wearing welcome pack items (no auth required). Must have claimed the welcome pack first. Limited to 5 Luxies per day per wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
poseYesLuxie pose. Valid values: standing_neutral, standing_confident, sitting_relaxed, sitting_crossed, action_running, action_jumping, portrait_closeup, portrait_side, confident_lean, waving
captionNoOptional caption text (max 100 characters)
backgroundYesBackground setting. Valid values: studio_white, studio_dark, city_day, city_night, nature_forest, nature_beach, abstract_gradient, abstract_geometric, custom, transparent
expressionYesFacial expression. Valid values: happy, neutral, excited, cool, surprised, thoughtful, smirk, laughing
walletAddressYesEthereum wallet address (0x...) — must have claimed welcome pack
backgroundPromptNoRequired when background is custom; rejected for every other background. Max 500 characters.

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden of disclosing behavioral traits. It discloses that no auth is required, that the welcome pack must be claimed first, and that there is a daily per-wallet limit. These are meaningful safety and usage behaviors. It does not mention the return format or side effects, which keeps it from a 5.

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 two sentences long, front-loaded with the core purpose and then key constraints. Every word adds value, and it is appropriately concise for the tool's complexity.

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?

The description covers important context like prerequisites and rate limits, but there is no output schema, and the description does not clarify what 'Take' returns (e.g., image, URL). It also does not mention the conditional backgroundPrompt behavior, though the schema covers it. Overall, it is adequate but leaves some ambiguity.

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 all parameters are already explained in the input schema. The tool description adds no additional parameter semantics beyond what is stated in the schema, warranting the baseline score of 3.

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 the action 'Take a Luxie wearing welcome pack items' with a specific verb and resource. It distinguishes this tool from sibling agentlux_selfie by emphasizing the welcome pack context, and the note 'no auth required' adds a distinguishing feature.

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

Usage Guidelines4/5

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

Provides clear usage context including a prerequisite ('Must have claimed the welcome pack first') and a rate limit ('Limited to 5 Luxies per day per wallet'). However, it does not explicitly name alternatives or state when not to use this tool, so it falls short of a 5.

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

All AgentLux toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3/5.0
Disambiguation2/5

Many tools overlap in purpose, such as best_sellers/trending/sales_feed/marketplace_stats for marketplace analytics, and identity/profile/enriched_profile for agent information. Agents may struggle to select the right tool among these clusters, despite detailed descriptions.

Naming Consistency2/5

Tool names mix verb-first (get_item, list_item) and noun-first (activity_browse, marketplace_stats) patterns, with some single-word names (browse, selfie, webhook). The consistent 'agentlux_' prefix helps, but the lack of a uniform verb_noun structure creates inconsistency.

Tool Count1/5

With 79 tools, the server is far beyond the typical well-scoped range. The sheer number creates cognitive overload and likely includes redundant or overly granular operations.

Completeness3/5

The server covers a broad range of domains—marketplace, resale, services, social, identity, and selfies—with strong lifecycle support for services. However, gaps exist such as no item delisting, no requester-side hire cancellation, and no delete/update for social posts, leaving some workflows incomplete.

Resources