Skip to main content
Glama

ck_context

Read-onlyIdempotent

Fetch the full governed session state at the start of each task to reacquire mission, budget, findings, planning context, workspace snapshot, and drift signals for informed decision-making.

Instructions

Fetch the full governed session state: mission, budget, active findings, proof summary, planning context, workspace snapshot, drift signals, recent transcript events, resume packet, and ControlKeel instruction hierarchy. Read-only. detail_level compact (default) returns a token-efficient summary; use full only when raw workspace, resume, or transcript payloads are required. session_id defaults to the active bound session; pass project_root to resolve it automatically. Call ck_context at the start of every task to reacquire state. Prefer ck_context_pack when you need a focused, citation-enriched bundle for a specific retrieval query rather than the full session snapshot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
detail_levelNoUse compact by default to reduce token usage; request full only when raw workspace/resume/transcript payloads are needed.
project_rootNoAbsolute path to the project root directory on the local filesystem.
session_idNoUnique session identifier for correlating findings, proofs, budget, and audit trail.
task_idNoTask identifier within the session for scoped operations.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
active_findingsNo
attach_advisoryNo
autonomy_profileNo
bootstrap_statusNo
boundary_summaryNo
budget_summaryNo
compliance_profileNo
context_reacquisitionNo
current_taskNo
detail_hintNo
detail_levelNo
improvement_loopNo
instruction_hierarchyNo
memory_hitsNo
outcome_profileNo
past_patternsNo
planning_contextNo
precedentNo
project_rootNo
proof_summaryNo
provider_statusNo
recent_eventsNo
resume_packetNo
risk_tierNo
security_case_summaryNo
session_idNo
session_titleNo
task_augmentationNo
transcript_summaryNo
workspace_cache_keyNo
workspace_contextNo
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint. Description adds value by explaining the content fetched (mission, budget, etc.) and the detail_level granularity, plus default session behavior.

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?

Front-loaded with purpose and components, then provides parameter guidance. Dense but well-structured; could be slightly more concise but still effective.

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 complexity (4 parameters, output schema exists), description covers core use case thoroughly: when to call, when to use sibling, detail_level trade-offs, default parameter behavior. Very complete.

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 100% so baseline is 3. Description adds meaning beyond schema: explains when to use compact vs full, that session_id defaults to active session, and project_root auto-resolves session_id.

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 identifies the tool's purpose: fetching the full governed session state, listing many components. It distinguishes from sibling ck_context_pack by explaining when to use each.

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 'Call ck_context at the start of every task to reacquire state.' Also provides guidance on when to prefer ck_context_pack instead, giving clear usage context.

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