Skip to main content
Glama

ck_context_pack

Build a compact, citation-enriched context bundle for the current task by combining task facts, proof state, and memory excerpts using an optional query.

Instructions

Build a compact, citation-enriched context bundle for the current session and task by combining task facts, proof state, resume highlights, and ranked memory excerpts. Read-only. query is an optional retrieval query; when omitted, ControlKeel synthesizes one from the current task title and session context. top_k controls how many memory hits to include (default 5). detail_level compact (default) keeps the bundle token-efficient. Prefer ck_context_pack over ck_context when you need a focused, query-driven bundle for a specific sub-task rather than the full session snapshot. Use ck_context at the start of a session for full mission state; use ck_context_pack mid-task to fetch targeted prior knowledge.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
detail_levelNo
project_rootNoAbsolute path to the project root directory on the local filesystem.
queryNoOptional explicit retrieval query. When omitted, ControlKeel synthesizes one from the current task and session.
session_idNoUnique session identifier for correlating findings, proofs, budget, and audit trail.
task_idNoTask identifier within the session for scoped operations.
top_kNoMaximum number of top-ranked results to return.
Behavior4/5

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

Discloses read-only nature upfront and explains key behaviors: query optionality with automatic synthesis, default top_k (5) and detail_level (compact), and token-efficiency goal. No annotations exist, so description carries full burden; minor gap is lack of explicit statement about no side effects beyond 'Read-only'.

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 concise sentences: first states purpose and read-only nature, second explains query parameter behavior, third gives usage guidelines. No redundant words, front-loaded with key information.

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?

Covers purpose, parameter behavior, and usage guidance adequately for a tool with 6 parameters and no output schema. Minor omission: does not specify behavior when both query and task context are absent. Still highly complete given complexity.

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?

Adds significant value beyond schema descriptions: explains query synthesis behavior, default values for top_k and detail_level, and token-efficiency implication. Schema covers 5/6 parameters with descriptions, but description enriches them with usage context and defaults.

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 specifies the verb ('Build'), resource ('compact, citation-enriched context bundle'), and scope ('current session and task'). It distinguishes from sibling tool 'ck_context' by explaining it's for focused, query-driven sub-task bundles vs. full session snapshots.

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?

Explicitly states when to use this tool ('mid-task to fetch targeted prior knowledge') and when to use the alternative ('Use ck_context at the start of a session'). Provides clear preference guidance with specific conditions.

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