Skip to main content
Glama

ck_task

Manage governed tasks within a session: retrieve status, claim, complete, send heartbeat, log quality checks, or submit reports.

Instructions

Manage governed tasks within a session. Six modes: status (return task details for a given task_id); claim (claim an available task for execution); complete (mark a task as done, blocked if unresolved findings exist); heartbeat (signal the agent is alive and working on a task); checks (record task quality check results); report (submit a task report with output and metadata).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoOperation mode that determines the tool behavior and return shape.
noteNoFreeform note for heartbeat mode.
checksNoArray of check result objects for checks mode.
outputNoStructured output payload for report mode.
statusNoTarget status for report mode (e.g., done, failed, blocked).
task_idNoTask identifier within the session for scoped operations.
metadataNoArbitrary key-value metadata for report mode.
progressNoProgress indicator for heartbeat mode.
session_idYesUnique session identifier for correlating findings, proofs, budget, and audit trail.
project_rootNoAbsolute path to project root.
execution_modeNoExecution mode for claim (e.g., local, external).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
titleNo
run_idNo
statusNo
claimedNo
resultsNo
task_idNo
recordedNo
reportedNo
completedNo
risk_tierNo
session_idNo
Behavior4/5

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

Annotations (readOnlyHint=false, etc.) are basic; description adds meaningful context: 'complete' mode is blocked if unresolved findings exist, and each mode has distinct behavior. No contradiction with annotations.

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 efficiently convey purpose and mode overview. No superfluous content; front-loaded with the core function.

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 complexity (11 params, 6 modes, output schema), the description covers main behaviors. Missing some edge-case details (e.g., error conditions beyond blocked complete) but adequate with schema and annotations.

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

Parameters4/5

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

Schema covers 100% of parameters with descriptions, so baseline is 3. The description adds value by linking parameters to specific modes (e.g., task_id for status/claim/complete, output for report), providing additional semantic grouping.

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 manages governed tasks within a session and lists six specific modes (status, claim, complete, heartbeat, checks, report) with brief explanations. This distinguishes it from sibling tools like ck_session or ck_finding.

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

Usage Guidelines3/5

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

The description implies usage through mode enumeration but lacks explicit guidance on when to use this tool vs alternatives, no 'when not to use' statements, and no mention of prerequisites or context for mode selection.

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/aryaminus/controlkeel'

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