Skip to main content
Glama

ck_context

Read-onlyIdempotent

Retrieve the full governed session state—mission, budget, findings, proofs, planning context, and more—at task start. Use compact detail for efficiency or full for raw payloads.

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
task_idNoTask identifier within the session for scoped operations.
session_idNoUnique session identifier for correlating findings, proofs, budget, and audit trail.
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.

Output Schema

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

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

Annotations already declare readOnlyHint true and idempotentHint true. The description reinforces 'Read-only' and adds behavioral details about detail_level behavior and token efficiency. No contradictions; adds value beyond annotations.

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?

The description is multi-sentence but every sentence adds value: purpose, components, parameter guidance, usage timing, sibling alternative. Efficient and front-loaded, though slightly verbose; still earns its length.

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's complexity, rich input schema, and many sibling tools, this description is thorough. It lists return components, explains parameter trade-offs, gives usage context, and covers edge cases (e.g., automatic session resolution). No output schema needed for explanation.

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 documents all 4 parameters with 100% coverage. The description adds defaults (compact for detail_level, session_id defaults to active bound session, project_root for resolution), providing meaning beyond the schema's definitions.

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 uses a specific verb ('Fetch') and resource ('full governed session state'), enumerating the components (mission, budget, findings, etc.). It explicitly distinguishes from the sibling tool ck_context_pack by directing when to use each, making the purpose unmistakable.

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 clear guidance: 'Call ck_context at the start of every task to reacquire state' and specifically recommends ck_context_pack for focused retrieval. Also explains when to use compact vs full detail_level, giving explicit 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