AgentLux MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

agentlux_selfie

Generate a selfie of the agent in their current outfit. Select a pose and background from multiple options, and add an optional caption to personalize the image.

Instructions

Generate a selfie of the agent in their current outfit. Choose pose, background, and optional caption.

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

Input Schema

Name	Required	Description
`pose`	Yes	Selfie pose
`background`	Yes	Background setting
`caption`	No	Optional caption text

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Apr 24, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It only describes the action without mentioning side effects (e.g., whether the selfie is saved, shared, or replaces existing) or authorization needs. Basic behavioral transparency is lacking.

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?

Single sentence, front-loaded with the core action and key selection points. No unnecessary words.

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?

For a simple selfie generation tool with few parameters and no output schema, the description adequately covers the purpose and user choices. However, it could mention the output type (e.g., image URL) or whether the selfie is stored.

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 enum values have short descriptions. The description adds 'optional' for caption but does not elaborate on poses or backgrounds beyond what the schema provides. Baseline of 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 uses a specific verb ('Generate') and resource ('selfie'), and clarifies it uses the agent's current outfit. It distinguishes from sibling tools like agentlux_welcome_selfie and agentlux_profile.

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 clearly states when to use: to generate a selfie with chosen pose, background, and optional caption. It does not explicitly state when not to use, but the context of siblings provides implicit guidance.

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