Skip to main content
Glama

edit_task

Edit an existing task in LifeUp by modifying its name, rewards, category, and other properties. Supports absolute or relative adjustments for XP and coins.

Instructions

Edit an existing task in LifeUp. You can modify task name, rewards, category, and other properties. When using exp_set_type="rel" or coin_set_type="rel", the exp and coin values are added to existing values. When using "abs" (absolute), values replace existing ones. This tool is blocked in SAFE_MODE.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTask ID to edit (required)
nameNoNew task name (optional)
contentNoNew task description/content (optional)
expNoNew XP reward value. Use exp_set_type to control if this is absolute or relative to current value (optional)
coinNoNew coin reward value. Use coin_set_type to control if this is absolute or relative to current value (optional)
skillsNoSkill/attribute IDs to receive XP rewards (optional)
categoryIdNoCategory/list ID to move task to (optional)
auto_use_itemNoAuto-use item rewards (optional)
task_typeNoTask type: 0=normal, 1=count task, 2=negative, 3=API task (optional)
target_timesNoTarget count for count tasks (optional, must be > 0 when task_type=1)
is_affect_shop_rewardNoWhether count affects shop rewards (optional)
importanceNoTask importance: 1=Low, 2=Normal, 3=High, 4=Critical (optional)
difficultyNoTask difficulty: 1=Easy, 2=Normal, 3=Hard, 4=Very Hard (optional)
frequencyNoRepeat frequency: 0=never, 1=daily, 2=weekly, etc. Special values: -1=Unlimited, -3=Ebbinghaus, -4=Monthly, -5=Yearly.
exp_set_typeNoHow to apply exp value: "absolute" replaces current, "relative" adds to current (optional, default: absolute)
coin_set_typeNoHow to apply coin value: "absolute" replaces current, "relative" adds to current (optional, default: absolute)
Behavior4/5

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

It explains the behavior of exp_set_type and coin_set_type (relative vs absolute) and mentions blocking in SAFE_MODE. No annotations are present, so the description covers essential behavioral aspects.

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?

Two sentences convey the main purpose and key behaviors efficiently, though a bit more structure (e.g., bullet points) could enhance 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?

With 16 parameters and no output schema, the description covers the main action and important behaviors but lacks details on return values, error cases, and prerequisites.

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%, but the description adds value by clarifying the effect of exp_set_type and coin_set_type beyond the schema, and hints at parameter interactions.

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 explicitly states it edits an existing task and lists modifiable properties, clearly distinguishing from sibling tools like create_task and delete_task.

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 when to use (editing existing tasks) and notes a constraint (blocked in SAFE_MODE), but does not explicitly exclude alternatives or provide when-not-to-use guidance.

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