Skip to main content
Glama

edit_subtask

Edit an existing subtask by specifying its parent task and the subtask to modify. Supports updating content, order, and rewards with absolute or relative value adjustments.

Instructions

Edit an existing subtask in LifeUp. You must specify both the parent task (using main_id, main_gid, or main_name) and the subtask to edit (using edit_id, edit_gid, or edit_name). Supports both absolute and relative value adjustments for coin and experience rewards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
main_idNoParent task ID (one of main_id, main_gid, or main_name is required)
main_gidNoParent task group ID (one of main_id, main_gid, or main_name is required)
main_nameNoParent task name (one of main_id, main_gid, or main_name is required)
edit_idNoSubtask ID to edit (one of edit_id, edit_gid, or edit_name is required)
edit_gidNoSubtask group ID to edit (one of edit_id, edit_gid, or edit_name is required)
edit_nameNoSubtask name to edit (one of edit_id, edit_gid, or edit_name is required)
todoNoUpdated subtask content/description (optional, max 200 characters)
orderNoPosition/order of subtask in the list (optional)
coinNoCoin reward (optional, 0-999999)
coin_varNoCoin variance/randomness (optional)
expNoExperience points reward (optional, 0-99999)
coin_set_typeNoHow to apply coin value: absolute (replace) or relative (add/subtract)
exp_set_typeNoHow to apply exp value: absolute (replace) or relative (add/subtract)
auto_use_itemNoAutomatically use/consume item rewards when subtask is completed (optional)
item_idNoItem ID for reward (optional)
item_nameNoItem name for reward (optional)
item_amountNoAmount of item to reward (optional, 1-99)
itemsNoArray of item rewards (optional)
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It describes identification and adjustment types but omits side effects, return values, authorization needs, or whether edits are reversible. Significant behavioral gaps remain.

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 three sentences, front-loaded with the main purpose, and every sentence adds necessary information without redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 18 parameters, no output schema, and no annotations, the description is insufficient. It lacks explanation of return values, error handling, or examples, making it incomplete for effective tool usage.

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 each parameter has a description in the schema. The tool description adds value by explaining absolute vs relative adjustments for coin and experience, but does not clarify other parameters beyond the schema.

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 tool edits an existing subtask in LifeUp, specifying the parent task and subtask identification. It distinguishes from siblings like create_subtask 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 Guidelines3/5

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

The description explains required parameters (parent and subtask) and supported value adjustments, but does not explicitly state when to use this tool versus alternatives like edit_task or create_subtask. Usage context is implied but without exclusions.

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