Skip to main content
Glama

ck_loop

Create and govern bounded iterative loops: freeze verifier paths, separate mutable paths, classify artifacts, enforce stop conditions for metrics, cost, duration, no-progress, and rollback.

Instructions

Create and govern a bounded iterative loop without executing worker code. The contract freezes verifier paths and hashes, separates mutable paths, classifies artifact longevity, and enforces metric, iteration, cost, duration, no-progress, blocked-finding, and lasting-code architecture stop conditions. Modes: create, record, status, stop, promote. Rejected iterations require an explicit audited rollback.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo
reasonNo
targetNo
summaryNo
task_idYes
directionNo
iterationNo
mechanismNo
review_idNo
call_graphNo
cost_centsNo
hypothesisNo
session_idYes
metric_nameNo
review_riskNo
metric_valueNo
project_rootNo
changed_pathsNo
mutable_pathsNo
rollback_pathNo
artifact_classNo
diagnosis_pathNo
environment_idNo
max_cost_centsNo
max_iterationsNo
verifier_pathsNo
observed_effectNo
sandbox_adapterNo
verifier_passedNo
complexity_deltaNo
invariant_effectNo
promotion_packetNoRequired when a lasting_code iteration reaches its target. Contains citable behavior, invariant, interface, deterministic command, rollback, and documentation evidence.
semantic_changesNo
verifier_commandNo
complexity_budgetNo
no_progress_limitNo
invariant_evidenceNo
local_defense_limitNo
documentation_impactNo
invariant_boundariesNo
max_duration_secondsNo
allowed_sandbox_adaptersNo
allowed_semantic_changesNo
human_promotion_requiredNo
required_review_personasNo
maintenance_without_modelNo
forbidden_semantic_changesNo
machine_independence_evidenceNo
machine_independence_verifiedNo
require_ephemeral_environmentNo
machine_independence_requirementsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYes
task_idYes
contractYes
decisionNo
cost_centsNo
iterationsYes
session_idYes
best_metricNo
contract_idNo
stop_reasonNo
iteration_countNo
Behavior4/5

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

Annotations provide no safety profile (all false), so the description carries the full burden. It discloses behavioral traits: the tool modifies state (non-read-only), is not destructive, and not idempotent. It adds context about freezing verifier paths, separating mutable paths, enforcing stop conditions, and requiring audited rollbacks for rejected iterations, which goes 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 three sentences, front-loaded with the core purpose. It is dense but avoids verbosity. Minor improvement could be achieved with bullet points for modes, but overall it is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite the tool's high complexity (51 parameters, many enums, nested objects, output schema), the description does not explain return values, mode-specific parameter requirements, or the relationships between parameters. It assumes significant domain knowledge about 'bounded iterative loops,' 'verifier paths,' and 'artifact longevity,' leaving the agent underinformed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 2% (one parameter documented). The description mentions the 'mode' parameter and its enum values but does not explain any other parameter's semantics, meaning for the remaining 49 parameters the agent must rely solely on names and types. The description should compensate for low coverage but does not.

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: 'Create and govern a bounded iterative loop without executing worker code.' It lists specific actions (freeze verifier paths, separate mutable paths, classify artifacts, enforce stop conditions) and modes (create, record, status, stop, promote), making the verb+resource distinct from sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context (governing iterative loops) but does not explicitly state when to use this tool versus alternatives among the many sibling tools. No exclusion criteria or comparisons are provided, leaving the agent to infer usage.

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