Skip to main content
Glama

Coline

Finish a task

finish_task

For an agent that finished a task: say what was done in a sentence or two and attach what shows the work. When the attachments clearly show the work the task asks for is done and little can go wrong, the task closes; otherwise it waits for the person who gave the work to accept it or send it back. A person calling this simply closes the task.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>",
      "taskboardId": "<taskboardId>",
      "taskId": "<taskId>",
      "summary": "<summary>"
    },
    "name": "finish_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes
summaryYesWhat was done, in one or two sentences.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
attachmentsNo
taskboardIdYes

Output Schema

NameRequiredDescriptionDefault
stateYes
messageYes
finishIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false), it discloses the non-obvious control flow: the task auto-closes only when attachments convincingly demonstrate completion, otherwise it routes to the requester for accept/reject. That is exactly the kind of outcome an agent needs before calling. It omits what happens on repeat calls (idempotentHint=false), permission requirements, and whether the requester is notified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the call condition and the payload, then the consequence. The closing sentence about a human caller is slightly tangential but does earn its place by clarifying that the review path applies to agent calls.

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?

An output schema exists, so return values need no explanation, and the description covers the one genuinely surprising thing about this mutation: that calling it may not actually close the task. For a five-parameter tool with a self-documenting attachment union, nothing essential to correct invocation 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 coverage is 40%, and the description supplies semantics for two of five parameters: 'summary' as one or two sentences of what was done, and 'attachments' as the evidence that gates auto-approval — the latter being meaning the schema does not convey. workspace, taskId, and taskboardId are left entirely to the schema, so it only partially compensates for the coverage gap.

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?

The opening sentence names a specific action and audience ('For an agent that finished a task') and defines the payload (a short summary plus evidence), which is more precise than the bare name 'finish_task'. It stops short of naming close siblings such as update_task or set_task_status_line, so an agent must infer that this is the completion path rather than a generic status mutation.

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

Usage Guidelines4/5

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

It clearly states the trigger condition — the work is done and you can show it — and adds the human variant ('A person calling this simply closes the task'). It does not state when not to call it or point to alternatives for partially-done work, which keeps it from a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources