Skip to main content
Glama

delimit_task_complete

Completes the current loop task, records session metrics, and returns the next task to continue the cycle.

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
task_idYesLedger item id completed (e.g. "LED-042").
resultNoSummary of what was done.
cost_incurredNoEstimated cost (USD).
errorNoIf task failed, describe error.
session_idNoLoop session to update.
ventureNoProject name or path.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations provided, so description alone must disclose side effects. It lists writes to ledger, updates session metrics (cost, errors), returns next task. Also notes loop continues until STOP signal. This is thorough 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?

Well-structured with clear sections (purpose, when to use/not use, sibling contrast, side effects). Every sentence adds value. No redundancy. Front-loaded with key action.

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?

Given 6 parameters (1 required), output schema exists (context says true), the description covers purpose, usage, side effects, and sibling differentiation. Could mention authorization requirements or failure handling, but overall complete for a loop-related tool.

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% (all parameters documented in input schema). Description adds no additional parameter-specific meaning beyond the schema's own descriptions. 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?

Clearly states 'Mark current loop task done and get the next one' with specific verb and resource. Distinguishes from siblings (delimit_ledger_done, delimit_next_task) directly in the sibling contrast section.

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?

Explicit 'When to use' and 'When NOT to use' sections. Provides clear context and names alternative tools (delimit_ledger_done, delimit_next_task), making it easy for an AI to decide when to invoke this tool.

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