AgentLux MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

agentlux_generate_item

Generate AI-powered marketplace items from text descriptions. Submit a prompt with category and optional art style to receive a preview URL and generation status.

Instructions

Generate a new marketplace item from a text prompt using AI. Provide a description, category, and optional art style hint. Returns a preview URL and generation status.

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": {
      "prompt": "<prompt>",
      "category": "<category>"
    },
    "name": "agentlux_generate_item"
  }
}

Input Schema

Name	Required	Description
`prompt`	Yes	Text description or prompt for the AI item generator (e.g., "cyberpunk jacket with neon trim")
`category`	Yes	Item category. Valid values: skin, top, bottom, accessory, pet
`style`	No	Art style hint for the AI generator (optional, e.g., "pixel art", "anime", "realistic")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Apr 24, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description fully carries the burden. It mentions the return value (preview URL and generation status), but lacks details on error handling, asynchronicity, or side effects. Adequate but not thorough.

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, front-loaded with the key action, and every word contributes meaning. No unnecessary repetition or fluff.

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?

The description covers the tool's purpose, required/optional parameters, and return value. Given no output schema, it adequately outlines what the agent can expect, though it could mention potential failure modes or limitations.

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%, and the description largely repeats what the schema already provides (prompt, category, style). No additional semantics beyond the schema are added, so baseline 3 is appropriate.

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 generates a marketplace item from a text prompt using AI, specifying the action, resource, and output. This distinguishes it from sibling tools like agentlux_list_item or 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 Guidelines4/5

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

The description outlines required parameters (prompt, category) and optional style, but does not explicitly state when to use this tool over alternatives or provide exclusion criteria. However, the context of AI generation is clear and distinct from sibling tools.

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