Skip to main content
Glama

LogNexus State: Finish subtask and mark completed

lognexus_state_finish_task

Mark a subtask as completed in LogNexus persistent state and return the updated state after its work is committed and Git Note attached.

Instructions

Mark a subtask as completed in the persistent state and return the updated state. Equivalent to 'lognexus state finish-task '. Use when the subtask work has already been committed and its Git Note attached. Not for creating the commit itself (use lognexus_commit with finishTask: true, which finishes the task atomically) and not for editing the contract (use lognexus_state_set_task).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "taskId": "T1"
    },
    "name": "lognexus_state_finish_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYesSubtask identifier, e.g. 'T1'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.6
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "taskId": "T1"
      +  }
      +]
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the mutation, its precondition, and that an updated state is returned, plus the atomic alternative. It stops short of stating idempotency, what happens if taskId does not exist, or whether completion is reversible.

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 sentences, each load-bearing: purpose and return, CLI equivalent, then when-to-use and when-not-to-use. Front-loaded with the action and no filler.

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 one-parameter state mutation with no output schema, the definition covers purpose, precondition, and alternatives well. The one gap is that 'return the updated state' does not describe the shape of that state, which the agent cannot infer without an output schema.

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% and the single taskId parameter is documented with an example ('T1'), so the description adds nothing beyond it. Baseline 3 is appropriate when the schema fully documents the only parameter.

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?

States a specific verb and resource: mark a subtask completed in persistent state and return the updated state. It also names the CLI equivalent and explicitly distinguishes itself from lognexus_commit and lognexus_state_set_task, so an agent can separate it from siblings without reading schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives an explicit precondition ('when the subtask work has already been committed and its Git Note attached') and two named exclusions with the correct alternatives: lognexus_commit with finishTask:true for atomic finishing, lognexus_state_set_task for contract edits.

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