Skip to main content
Glama

ck_goal

Record, list, or update durable goals with status and scope, keeping long-running intent explicit, citable, and reviewable across sessions. Tracks task, session, or workspace horizons.

Instructions

Record, list, or update durable governed goals so long-running intent stays explicit, citable, and reviewable across sessions. Three modes: record (write — creates a new goal); list (read-only — returns goals filtered by status and horizon); update_status (write — updates an existing goal's status or progress). Required: session_id and mode. For record: provide goal (the statement text) and optionally title, horizon (task/session/workspace), and tags. For update_status: provide goal_id and the new status. horizon controls scope: task for short-lived intent, session for the current session, workspace for persistent cross-session goals. Use ck_goal for structured multi-session intent that should be explicitly tracked and reviewed. Use ck_memory_record for general decisions or notes not requiring status tracking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoFull content body with detailed information.
goalNoThe goal statement text.
modeYesOperation mode that determines the tool behavior and return shape.
tagsNo
limitNoMaximum number of results to return.
titleNoHuman-readable title for display and search.
statusNoCurrent status for filtering or updating.
goal_idNoUnique identifier of an existing goal to update.
horizonNoTemporal scope of the goal: task, session, or workspace.
summaryNoBrief human-readable summary of the record.
task_idNoTask identifier within the session for scoped operations.
metadataNo
source_idNoUnique identifier of the source system or record.
session_idYesUnique session identifier for correlating findings, proofs, budget, and audit trail.
source_typeNoOrigin category of the record (e.g., developer, tool_output, human_review).
progress_noteNoNote about progress toward the goal.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalNo
goalsNo
titleNo
statusNo
goal_idNo
horizonNo
progress_noteNo
Behavior5/5

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

Describes three modes with different read/write behaviors, explains horizon scope, and does not contradict annotations (readOnlyHint=false indicates writes are possible).

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?

Single paragraph is clear and front-loaded, but could use slight restructuring (e.g., bullet points) for easier scanning. No wasted sentences.

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 complexity (3 modes, many optional params) and presence of output schema, description covers all major behavioral aspects and usage context comprehensively.

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 coverage is high (88%); description adds meaning by explaining mode-dependent required fields, horizon roles, and differentiation from sibling. Adds value beyond schema.

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?

Description clearly states it records/lists/updates goals, specifies three modes, and distinguishes from sibling ck_memory_record by stating use case.

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 guidance for each mode, required parameters per mode, and compares with ck_memory_record for when not to use 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/aryaminus/controlkeel'

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