Skip to main content
Glama

create_achievement

Create custom achievements with unlock conditions, experience, coin, skill, and item rewards. Set optional conditions like tasks, pomodoros, or coins. Achievements are locked by default.

Instructions

Create a new custom achievement with unlock conditions and rewards. Requires achievement name and category ID. Optionally specify unlock conditions (JSON array), experience/coin rewards, skill rewards, item rewards, and appearance settings. Created achievements are locked by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesAchievement name (required, max 100 characters)
category_idYesAchievement category/list ID (required)
descNoAchievement description (optional, max 500 characters)
conditions_jsonNoUnlock conditions as JSON array (optional). Format: [{"type":7,"target":1000000}]. Common types: 0=task completion, 3=pomodoro, 6=daily streak, 7=coins, 13=skill level, 14=life level
expNoExperience points reward (optional). IMPORTANT: Must specify skills array to apply XP to attributes.
coinNoCoin reward (optional, 0-999999)
coin_varNoCoin reward variation/randomness (optional)
skillsNoSkill/attribute IDs to receive XP rewards. Required when setting exp parameter. Without skills, XP cannot be applied.
itemsNoItem rewards (optional). Format: [{"item_id":1,"amount":2}]
item_idNoSingle item reward ID (optional, alternative to items array)
item_amountNoSingle item reward amount (optional, 1-99)
secretNoHidden achievement (optional, default: false)
colorNoTitle color in hex format (optional, e.g., "#66CCFF")
unlockedNoCreate as already unlocked (optional, default: false)
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that created achievements are locked by default and that XP requires the skills array. However, it does not explain whether the creation is idempotent, the response format, or any side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single paragraph of four sentences, efficiently front-loading the core action and then listing options. It avoids redundancy but could use brief bullet points for readability.

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?

Given 14 parameters and no output schema, the description covers the essential creation logic and critical constraints (XP+skills). However, it omits return values, error handling, and prerequisites beyond required fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds context by emphasizing that XP requires skills and that achievements are locked by default. It also summarizes optional parameters, which helps the agent prioritize.

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 action ('Create') and resource ('achievement') and specifies 'custom achievement with unlock conditions and rewards'. Sibling tools like 'update_achievement' and 'delete_achievement' make the distinction obvious.

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 mentions required fields (name, category_id) and optional parameters, and notes that achievements are locked by default. However, it does not provide explicit guidance on when to use this tool versus alternatives like 'update_achievement' or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/derekprovance/lifeup-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server