Skip to main content
Glama

ck_context_pack

Read-onlyIdempotent

Builds a compact, citation-enriched context bundle from task facts, proof state, resume highlights, and ranked memory excerpts. Fetches targeted prior knowledge mid-task with 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
queryNoOptional explicit retrieval query. When omitted, ControlKeel synthesizes one from the current task and session.
top_kNoMaximum number of top-ranked results to return.
task_idNoTask identifier within the session for scoped operations.
session_idNoUnique session identifier for correlating findings, proofs, budget, and audit trail.
detail_levelNo
project_rootNoAbsolute path to the project root directory on the local filesystem.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
task_idNo
hit_countNo
count_onlyNo
session_idNo
context_packNo
detail_levelNo
factual_onlyNo
generated_atNo
tag_distributionNo
excluded_ids_countNo
retrieval_strategyNo
semantic_availableNo
Behavior4/5

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

Description states 'Read-only' which aligns with annotations (readOnlyHint=true, destructiveHint=false). It also explains default behaviors for omitted query and detail_level. Adds value beyond annotations by clarifying synthesis of query and default detail_level.

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?

Four sentences: first states purpose, second outlines parameters, third gives usage guidance. No redundant words. All information is front-loaded and critical for agent decision.

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 the tool has 6 parameters, output schema, and annotations, the description covers purpose, parameter behaviors, defaults, and usage context. It is complete and does not need to explain return values due to output schema.

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 description coverage is 83%, so baseline is 3. Description adds meaningful defaults and behavior for query (synthesized when omitted), top_k (default 5), and detail_level (compact default). This enriches understanding beyond the schema descriptions.

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 builds a compact, citation-enriched context bundle. It uses specific verbs and resources ('Build a ... context bundle') and distinguishes itself from the sibling tool ck_context by specifying use cases (mid-task vs session start).

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 guides when to use this tool over ck_context: '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... use ck_context_pack mid-task.' This provides clear context and alternatives.

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