Skip to main content
Glama

complete_task

Mark a claimed task as done without review for trivial or mechanical tasks, and provide a summary for dependent agents.

Instructions

Mark your claimed task done WITHOUT review (for trivial/mechanical tasks).

For anything substantive, prefer submit_for_review so another agent checks the work. summary is what future briefings will show to agents whose tasks depend on this one — write it for them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes
agent_idYes
summaryYes
artifactsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
project_idYes
titleYes
descriptionNo
roleNoSuggested agent role, e.g. 'implementer'.any
priorityNo1 = highest, 3 = lowest.
statusNoopen
depends_onNo
claimed_byNo
lease_expires_atNo
iterationNoHow many review round-trips this task has had.
summaryNoCompletion summary written by the finishing agent.
artifactsNoPaths/URLs produced by the task.
created_atYes
updated_atYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses that no review happens, but does not mention permissions, irrversibility, or other side effects. The mention that summary is for future briefings adds some transparency, but more detail on what happens when completing a task would improve clarity.

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 two sentences long, front-loaded with the core action and condition, and includes a helpful note on the summary. No redundant information.

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?

The output schema exists but is not shown; still, the description covers the core behavior and usage. However, without explaining all parameters, the definition is incomplete for agents needing to supply correct inputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It only explains the 'summary' parameter (for future briefings). The 'task_id', 'agent_id', and 'artifacts' parameters are not addressed, leaving their meaning and format ambiguous despite self-explanatory names.

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 clearly states the tool's purpose: 'Mark your claimed task done WITHOUT review (for trivial/mechanical tasks).' It uses a specific verb and resource, and distinguishes from the sibling tool 'submit_for_review'.

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?

The description explicitly tells when to use this tool versus alternatives: 'For anything substantive, prefer submit_for_review.' It also provides guidance on the summary parameter: 'write it for them.' This makes usage context clear.

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/H2SO4620/forgeswarm'

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