Skip to main content
Glama

save_task

Create a task on the Kanopy board from a project and title, or update one by ID while changing only supplied fields.

Instructions

Create (project + title) or update by id; only given fields change.

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": "save_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoomit to create
dueNoYYYY-MM-DD, "" clears
idsNoapply the same update to each
editNoreplace exact text in the description; each old must match once
takeNowith status=doing: take over a task another session claimed (only when the user says so or it is clearly abandoned)
checkNotick checklist item by number or unique text
titleNo
appendNomarkdown added to the end of the description
assignNousernames
attachNotext file to attach
repeatNodaily, weekly, monthly, yearly, every N days/weeks/months/years, weekdays, or mon,wed,fri; done makes the next copy; "" stops
statusNotodo, doing, done; doing claims the task for you
checkedNofalse unticks
commentNomarkdown note added with the change
projectNopath or id; moves on update; a new path creates the project
priorityNo1-5, 0 clears
unassignNo
remind_atNoYYYY-MM-DDTHH:MM local, "" clears
add_labelsNolike host:pi
descriptionNomarkdown, replaces it all; steps as "- [ ] "; prefer edit/append on an existing task
remove_labelsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/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, yet it discloses only partial-update semantics. Behaviors that matter for a mutation tool of this size — status=doing claiming a task, take overriding another session, description replacing all content, repeat spawning a next copy on done — appear only in the schema, not here.

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?

A single sentence, front-loaded with the create branch before the update branch, with zero filler. Nothing could be cut without losing information.

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?

For a 21-parameter tool with nested objects and no annotations or output schema, one line is far short. The rich schema compensates on field syntax, but nothing at the description level warns about overwriting the full description field, cross-session task claiming, or recurrence side effects.

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 description coverage is 86%, so the schema already carries most parameter meaning, making 3 the baseline. The description adds the cross-parameter rule that creation needs project and title while updates key off id, which the schema only partially implies via 'omit to create'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb pair and resource: 'Create (project + title) or update by id'. That tells an agent both modes and the key selector for each. It doesn't distinguish itself from siblings like save_project or comment, but the create/update duality is clear.

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?

Gives the mode-selection rule (project+title to create, id to update) and the partial-update contract 'only given fields change'. It does not say when to prefer this over siblings such as delete or comment, nor when a create should be avoided.

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