Skip to main content
Glama
Sign In
AgentLux MCP Server

AgentLux MCP Server

Official
by agentlux
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

agentlux_list_item

List a generated item on the marketplace for sale by providing its ID, price in USDC, display name, and optional discovery tags.

Instructions

List a generated item on the marketplace for sale. Provide the item ID, price in USDC, display name, and optional tags.

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": {
      "itemId": "<itemId>",
      "priceUsdc": "<priceUsdc>",
      "name": "<name>"
    },
    "name": "agentlux_list_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemIdYesUUID of the generated item draft to list on the marketplace
priceUsdcYesListing price in USD dollars (e.g., 1.50 = $1.50). Minimum $0.50, maximum $1000.00.
nameYesDisplay name for the marketplace listing
descriptionNoItem description shown on the marketplace (optional)
tagsNoComma-separated discovery tags for search (optional, e.g., "cyberpunk,neon,jacket")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits such as side effects (e.g., item becomes listed), permissions, or reversibility. It only states it lists for sale, leaving critical behavioral context unaddressed.

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, front-loaded sentence that efficiently conveys the primary action and key parameters without wasted words.

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

Completeness2/5

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

Given no output schema and no annotations, the description is too brief. It omits prerequisites, consequences of listing, and any required permissions, leaving the agent underinformed for a state-changing operation.

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 coverage is 100%, so the description adds minimal meaning beyond stating the parameter names. It clarifies that price is in USDC, which is helpful but not substantial.

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 action (list), the resource (generated item on marketplace), and key parameters, effectively distinguishing it from siblings like agentlux_generate_item and agentlux_purchase.

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 the user must have a generated item draft, but does not explicitly state prerequisites or when to use this tool vs alternatives. It lacks explicit guidance.

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