Skip to main content
Glama

create_task

Create a new task in LifeUp with optional experience points, coins, subtasks, and custom settings for rewards and repetition.

Instructions

Create a new task in LifeUp. Specify task name and optional rewards (experience points and coins). When setting XP, you must provide skillIds to indicate which attributes receive the XP. The task will be created as an active task in your LifeUp app. This tool will prompt you to confirm the server is running if it cannot connect.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesTask name (required, max 200 characters)
expNoExperience points reward (optional, non-negative). If specified, must provide skillIds to indicate which attributes receive the XP. When omitted, defaults to 0.
skillIdsNoSkill/attribute IDs to receive XP rewards. Required when setting exp parameter. Supports multiple values (e.g., [1, 2, 3]).
coinNoCoin reward (optional, non-negative)
categoryIdNoCategory/list ID to place the task in (optional)
contentNoTask description/content (optional, max 1000 characters)
auto_use_itemNoAutomatically use/consume item rewards when task is completed (optional, defaults to false)
task_typeNoTask type: 0=normal (default), 1=count task, 2=negative task, 3=API task. Count tasks can be completed multiple times. Requires LifeUp v1.99.1+
target_timesNoTarget count for count tasks (required when task_type=1, must be > 0). Example: Set to 5 to create a task that needs to be completed 5 times.
is_affect_shop_rewardNoWhether count affects shop item reward calculations (optional, only valid when task_type=1, defaults to false)
importanceNoTask importance level: 1=Low, 2=Normal, 3=High, 4=Critical (optional, defaults to 1)
difficultyNoTask difficulty level: 1=Easy, 2=Normal, 3=Hard, 4=Very Hard (optional, defaults to 1)
subtasksNoArray of subtasks to create with the main task (optional, max 50 subtasks)
frequencyNoRepeat frequency: 0=never, 1=daily, 2=weekly, etc. Special values: -1=Unlimited, -3=Ebbinghaus, -4=Monthly, -5=Yearly.
Behavior3/5

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

The description discloses that the task becomes active, the need for skillIds with XP, and a server connection prompt. However, with no annotations, it lacks details on auth requirements, rate limits, or side effects on other data.

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 brief and front-loaded with the core purpose. It efficiently conveys key constraints in a single paragraph, though it could be slightly more structured (e.g., bullet points for conditions).

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 14 parameters, no output schema, and no annotations, the description adequately covers the main behavior, constraints, and a connection note. It misses return value information but is complete enough for a creation tool.

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%, so the schema already documents all parameters. The description adds minimal extra meaning beyond reiterating the XP-skillIds relationship and max character limits, resulting in marginal added value.

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 'Create a new task' and the resource 'LifeUp', and distinguishes the tool from siblings like edit_task, delete_task, list_all_tasks by focusing on creation.

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 provides clear context for use (creating a task) and mentions a key prerequisite (skillIds required when setting XP). However, it does not explicitly exclude alternatives or state when not to use this tool over siblings like create_subtask.

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