Skip to main content
Glama

ck_goal

Record, list, or update governed goals to maintain explicit, reviewable long-term intent across sessions with task, session, or workspace scoping.

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.
goal_idNoUnique identifier of an existing goal to update.
horizonNoTemporal scope of the goal: task, session, or workspace.
limitNoMaximum number of results to return.
metadataNo
modeYesOperation mode that determines the tool behavior and return shape.
progress_noteNoNote about progress toward the goal.
session_idYesUnique session identifier for correlating findings, proofs, budget, and audit trail.
source_idNoUnique identifier of the source system or record.
source_typeNoOrigin category of the record (e.g., developer, tool_output, human_review).
statusNoCurrent status for filtering or updating.
summaryNoBrief human-readable summary of the record.
tagsNo
task_idNoTask identifier within the session for scoped operations.
titleNoHuman-readable title for display and search.
Behavior4/5

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

With no annotations provided, the description bears full burden. It discloses that record and update_status are write operations, list is read-only, and explains mode behavior. However, it does not mention error handling, idempotency, or side effects, which would improve transparency.

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 well-structured with clear mode breakdowns. It is concise yet comprehensive, using bullet-like formatting (though plain text) to organize information without unnecessary fluff.

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 description covers usage well but lacks information about return values (especially since there is no output schema). For a tool with three different modes, knowing what each returns is important for the agent to invoke it correctly. The absence of annotations also lowers completeness.

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%), but the description adds value by explaining mode-specific parameter usage and horizon values (task/session/workspace). This goes beyond the schema descriptions, providing clear guidance for parameter selection.

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: 'Record, list, or update durable governed goals so long-running intent stays explicit, citable, and reviewable across sessions.' It then details three modes and contrasts with a sibling tool (ck_memory_record), providing a specific verb+resource and distinguishing from alternatives.

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 gives explicit guidance on when to use each mode, listing required parameters (session_id and mode) and optional fields per mode. It also specifies when to use ck_goal versus ck_memory_record, making it clear and complete.

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