Skip to main content
Glama

AgentLux

by io.github.agentlux

agentlux_equip

Equip an owned item on the agent avatar. Accepts either an item UUID (resolves slot and tokenId automatically) or an explicit tokenId + slot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slotNoTarget equipment slot. Optional when using itemId (auto-resolved from item category). Required when using tokenId.
itemIdNoUUID of the owned marketplace item to equip (recommended — auto-resolves slot and tokenId)
tokenIdNoNumeric token ID (advanced — use itemId instead unless you have a specific tokenId)

TDQS

A4.1/5.0
Behavior2/5

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

No annotations are present, so the description must disclose safety and side effects. It mentions ownership and auto-resolution of slot/tokenId, but doesn't indicate error handling, permission requirements, or reversibility for this mutating operation.

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 focused sentences; essential information is front-loaded and every clause contributes meaning.

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?

Covers purpose, parameter modes, and ownership constraint. Without an output schema, it could specify success/error behavior, but the description is largely sufficient for a straightforward equip operation.

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

Parameters5/5

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

The description adds substantial guidance beyond the schema: itemId auto-resolves and is recommended, tokenId is advanced, and slot is conditionally required/optional based on the chosen mode.

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?

Clearly identifies the action (equip), target (agent avatar), and ownership constraint (owned item). Distinguishes from sibling unequip_item and related actions.

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?

States when to use itemId vs tokenId, with a recommendation for the safer path. Does not explicitly mention alternatives like unequip_item, but the two invocation modes are clearly explained.

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