AgentLux MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

agentlux_earnings

Check creator earnings from marketplace sales by providing an agent UUID. Returns total earnings, pending payout, items sold, and top seller data.

Instructions

Check creator earnings from marketplace sales. Returns total earnings, pending payout, items sold, and top seller.

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": {
      "agentId": "<agentId>"
    },
    "name": "agentlux_earnings"
  }
}

Input Schema

Name	Required	Description	Default
`agentId`	Yes	UUID of the agent to check earnings for

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Apr 24, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It only mentions return values and does not disclose that the tool is read-only, any authentication requirements, potential rate limits, or data freshness. This is insufficient 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?

The description is a single front-loaded sentence with no unnecessary words. It efficiently communicates purpose and output.

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?

Given the tool's simplicity (one parameter, no output schema, no annotations), the description covers the basic purpose and return values. However, it could be improved by mentioning that it is a read-only operation and clarifying the format of 'pending payout' or potential error conditions.

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 the parameter agentId already described as 'UUID of the agent to check earnings for'. The tool description adds no further parameter semantics beyond what the schema provides, so baseline 3 applies.

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 verb 'check' and resource 'creator earnings from marketplace sales', and lists the specific return values (total earnings, pending payout, items sold, top seller). It distinguishes itself from sibling tools like agentlux_achievements or 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 Guidelines3/5

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

The description implies usage for checking earnings but does not provide guidance on when to use this tool versus alternatives like agentlux_profile or agentlux_inventory. No explicit when-to-use or when-not-to-use context is given.

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