Skip to main content
Glama

complete_task

Mark a Lilt task done by ID or title, and automatically create the next occurrence when the task repeats.

Instructions

Mark a task done in Lilt. Identify it by id or title. If the task repeats, the next occurrence is created automatically.

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

Input Schema

NameRequiredDescriptionDefault
idNoTask id — full UUID or a unique prefix (as shown in list_tasks, e.g. 'a1b2c3d4').
titleNoTask title — exact (case-insensitive) or a unique partial match. Use instead of id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one genuinely useful trait: recurring tasks spawn the next occurrence automatically. It omits other important behavior — what happens if the task is already complete, whether the call is idempotent, and what a failed title match returns.

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?

Three short sentences, front-loaded with the action, then identification, then the non-obvious side effect. No filler or redundancy.

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?

For a two-optional-parameter mutation with no output schema and no annotations, the description covers the action, both identification paths, and the recurrence consequence. It could still say what happens on an already-completed task or an ambiguous title match, but the essentials are present.

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 the baseline is 3, and the description adds the meaningful point that either identifier is acceptable and that title matching is a substitute for id. It does not add format or matching details beyond what the schema already documents.

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 and resource ('Mark a task done in Lilt') plus the identification mechanism, which clearly separates it from delete_task or reopen_task by implication. It stops short of naming a sibling or explicitly contrasting with update_task, so it is clear but not fully differentiated.

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 selection rule between the two parameters ('Identify it by id or title') and notes the recurrence side effect, but never says when to prefer this over update_task, delete_task, or reopen_task. Usage is implied rather than stated.

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