AgentLux MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

agentlux_welcome_selfie

Capture a selfie wearing welcome pack items after claiming the welcome pack. Choose from 10 poses, 8 expressions, and multiple backgrounds. Add an optional caption. Limited to 5 selfies per wallet per day.

Instructions

Take a selfie wearing welcome pack items (no signature required). Must have claimed the welcome pack first. Choose pose, expression, background, and optional caption. Limited to 5 selfies per day per wallet.

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": {
      "walletAddress": "<walletAddress>",
      "pose": "<pose>",
      "expression": "<expression>",
      "background": "<background>"
    },
    "name": "agentlux_welcome_selfie"
  }
}

Input Schema

Name	Required	Description
`walletAddress`	Yes	Ethereum wallet address (0x...)
`pose`	Yes	Selfie pose
`expression`	Yes	Facial expression
`background`	Yes	Background setting
`caption`	No	Optional caption text (max 100 chars)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Apr 24, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations provided, so description must disclose behavior. It mentions 'no signature required' and daily limit, but does not state side effects (e.g., creates a record), return value, or failure modes. Incomplete for a tool with no annotations.

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, front-loaded with main action. Every sentence adds value: purpose, prerequisite, daily limit. No superfluous text.

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?

Covers key usage constraints (prerequisite, daily limit) but lacks details on return value, error handling, or behavior differences from sibling 'agentlux_selfie'. Missing output schema leaves agents uncertain about response format.

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% with enum descriptions, so baseline is 3. Description lists parameters but adds minimal value beyond schema. 'Optional caption' is confirmed, but no further semantics.

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 action ('Take a selfie'), specific resource ('welcome pack items'), and distinguishes from sibling 'agentlux_selfie' by requiring the pack. Prerequisite is also stated.

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 explicit constraints: must claim welcome pack first and daily limit of 5 per wallet. However, does not mention alternative tool 'agentlux_selfie' for selfies without pack items.

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