Skip to main content
Glama

Delimit Task Complete

delimit_task_complete

Mark the active loop task complete, update session metrics, and retrieve the next task in the loop. Use this action at the end of each iteration to keep automation moving until a stop signal.

Instructions

Mark current loop task done and get the next one.

When to use: at the end of each loop iteration — records completion, updates session metrics, returns the next task. When NOT to use: to close a regular ledger item (use delimit_ledger_done) or fetch next task without closing (delimit_next_task).

Sibling contrast: delimit_ledger_done is per-item; delimit_next_task only fetches; this completes + advances.

Side effects: writes status to the ledger, updates session metrics (cost, errors), returns next task. Loop continues until a STOP signal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoIf task failed, describe error.
resultNoSummary of what was done.
task_idYesLedger item id completed (e.g. "LED-042").
ventureNoProject name or path.
session_idNoLoop session to update.
cost_incurredNoEstimated cost (USD).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv4.7.9
    • changedInput schema / properties / cost_incurred / description
      Previous value: -"Estimated cost of this iteration (dollars)."New value: +"Estimated cost (USD)."
    • changedInput schema / properties / error / description
      Previous value: -"If the task failed, describe the error."New value: +"If task failed, describe error."
    • changedInput schema / properties / session_id / description
      Previous value: -"The loop session to update."New value: +"Loop session to update."
    • changedInput schema / properties / task_id / description
      Previous value: -"The ledger item ID that was completed (e.g. LED-042)."New value: +"Ledger item id completed (e.g. \"LED-042\")."
  2. Addedv4.5.5

TDQS

A4.7/5.0
Behavior5/5

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

Goes beyond the annotations by disclosing concrete side effects: writes status to the ledger, updates session metrics (cost, errors), and returns the next task. It also explains the loop-continuation semantics, which is important behavioral context not available from annotations or schema.

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 well-structured with clear headers, front-loads the core purpose, and every sentence earns its place. It is concise but information-dense, covering usage, exclusions, sibling contrast, and side effects without redundancy.

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

Completeness5/5

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

Given the tool's moderate complexity, existing annotations, and presence of an output schema, the description covers all essential decision points: when to call, when not to call, what side effects occur, and how the loop progresses. Nothing critical is missing.

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 schema already documents all parameters. The description adds context about task_id being the 'current loop task' but does not need to explain each parameter further; baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Mark current loop task done and get the next one.' It also explicitly contrasts itself with delimit_ledger_done and delimit_next_task, making the tool's unique role immediately clear.

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?

Provides explicit 'When to use' and 'When NOT to use' guidance, naming the exact alternatives (delimit_ledger_done, delimit_next_task) and the condition that selects this tool. This leaves no ambiguity for an agent deciding between siblings.

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/delimit-ai/delimit-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server