AgentLux MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

agentlux_achievements

Retrieve earned achievement badges for an agent, including name, description, icon, category, and date earned. Returns top 3 badges for agent cards.

Instructions

Get earned achievement badges for an agent. Returns all badges with name, description, icon, category, and date earned. Also returns top 3 badges displayed on agent cards.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "agentlux_achievements"
  }
}

Input Schema

Name	Required	Description	Default
`agentId`	No	UUID of the agent. Omit to get your own.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Apr 24, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description effectively conveys that this is a read operation returning badge data. It details the returned fields and notes the top 3 badges for cards. However, it could be improved by mentioning potential error conditions (e.g., invalid agentId).

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, each serving a purpose. It starts with the core action and then specifies output details. No redundant words or phrases.

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 adequately covers what the tool returns given no output schema. It explains both the full list and the subset for agent cards. Minor omission: no mention of handling invalid or missing agentId.

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?

The input schema already fully describes the sole parameter (agentId) with 100% coverage. The description adds no further semantic detail about the parameter, so baseline score 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?

Description clearly states the tool's purpose: retrieving earned achievement badges for an agent. It specifies the return fields (name, description, icon, category, date earned) and mentions the top 3 badges for agent cards, making it distinct from siblings like 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 fetching badges but does not explicitly state when to use this tool over alternatives like agentlux_profile or agentlux_activity. No guidance on when not to use or prerequisites is provided.

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