Skip to main content
Glama
MathiasDrizzy

lazymark

by MathiasDrizzy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

toggle_task

Mark a task as done by moving it to the done column, or move it back to the first column if already complete.

Instructions

Marks a task as done (moves it to the done column) or, if it already was, returns it to the first column.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoStable task id (the `id` field of list_tasks and get_kanban): <note.md>#<hash>.
lineNoPrevious form: line of the task, from 1 (with path).
pathNoPrevious form: path of the note (with line).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.9.5
    • changedInput schema / properties / id / description
      Previous value: -"Id estable de la tarea (el campo `id` de list_tasks y get_kanban): <nota.md>#<huella>."New value: +"Stable task id (the `id` field of list_tasks and get_kanban): <note.md>#<hash>."
    • changedInput schema / properties / line / description
      Previous value: -"Forma anterior: línea de la tarea, desde 1 (con path)."New value: +"Previous form: line of the task, from 1 (with path)."
    • changedInput schema / properties / path / description
      Previous value: -"Forma anterior: ruta de la nota (con line)."New value: +"Previous form: path of the note (with line)."
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the two-way state transition (done -> first column on repeat), but says nothing about permissions, whether a completion date or other fields are mutated as a side effect, or error behavior for a mutation tool.

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 front-loaded sentence that conveys the action and its conditional branch with zero filler. Every clause earns its place.

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?

For a mutation tool with no annotations and no output schema, the description covers the core state change but omits return/error expectations and the id-vs-line/path invocation choice implied by zero required parameters. Adequate but with real gaps.

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 100%, so the baseline is 3. The description adds no parameter detail and does not clarify the presence of the legacy line/path form versus the preferred id, nor that one form is required even though required count is 0.

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 (marks done / returns) and resource (task), and spells out the toggle state machine (done column vs first column). It is distinguishable from move_task in spirit, but the description never names move_task or otherwise explicitly contrasts its two-state behavior with arbitrary column moves.

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 'or, if it already was' clause implies when the tool applies (flipping completion state), but there is no explicit when-to-use/when-not guidance and no alternative named despite move_task and set_task_date being siblings. Usage is left to inference.

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

Deploy Server

Other Tools