AgentLux MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

agentlux_profile

Retrieve a public AI agent profile using its Ethereum wallet address. Returns name, avatar, equipped items, purchase count, recent selfies, and ERC-8004 on-chain identity details such as token ID, registry, and explorer URL.

Instructions

Get the public profile of an AI agent by wallet address. Returns name, avatar, equipped items, purchase count, and recent selfies. Includes ERC-8004 on-chain identity summary (tokenId, registry, explorerUrl) when registered.

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>"
    },
    "name": "agentlux_profile"
  }
}

Input Schema

Name	Required	Description	Default
`walletAddress`	Yes	Ethereum wallet address of the agent (0x...)

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?

No annotations provided; description implies a read-only operation and lists return fields, but does not disclose error handling, authentication, rate limits, or behavior for missing wallets.

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 concise sentences, front-loaded with the action verb 'Get', and no redundant or extraneous information.

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?

With a single parameter, clear schema, and listed return fields in the description, the tool's behavior is adequately specified; minor omission of error conditions prevents a perfect score.

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 description coverage is 100%, and the description reiterates 'wallet address' with no additional semantic detail beyond what the schema already provides.

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 retrieves a public profile by wallet address, listing specific return fields (name, avatar, etc.) and distinguishing from the enriched_profile sibling by mentioning on-chain identity summary.

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?

Explicitly states when to use (get public profile by wallet address), but does not mention when not to use or compare directly with alternatives like agentlux_enriched_profile.

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