Skip to main content
Glama

tcai_cycle

Execute a neuromorphic consciousness cycle that processes SNN signals through emotional memory and self-model loops. Optionally halt early when the recursive loop achieves sustained, stable satisfaction.

Instructions

Run one or more ACM cycles (the_consciousness_ai port): SNN signals → AKOrN binding → GNW ignition → qualia → emotion → reward shaping → emotional memory → self-model → second-order loop. Set stopWhenSatisfied to halt early once the recursive loop reaches a sustained satisfactory (converged, low-curiosity, stable) regime.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cyclesNoNumber of cycles (default 1; upper bound if stopWhenSatisfied)
rewardSignalNoTask feedback ∈ [−1,1]
noveltyNoSurprise/curiosity ∈ [0,1]
threatNo
controllabilityNo
predictionErrorNoWorld-model surprise (raw)
predictionConfidenceNo
narrativeNoAnnotation for the memory record
stopWhenSatisfiedNoHalt early when the second-order loop reports sustained satisfaction
epsFreeEnergyNoHalt threshold: absolute |ΔF| ≤ (nats, default 0.02)
relFreeEnergyNoHalt threshold: |ΔF| ≤ rel·F, scale-free (default 0.03)
minTaskQualityNoHalt threshold: realized task quality ≥ (default 0.6)
maxEpistemicNoHalt threshold: expected info gain ≤ (default 0.1)
satisfactionPatienceNoConsecutive satisfied cycles required to halt (default 3)
closedLoopNoEnable closed-loop actuation (AIF action drives the substrate); default on
setpointNoContinuous controller substrate setpoint to regulate toward (v2.9, default 0.3)
productionLoopNoClose the loop through the shared production SNN (read+write); default off (v2.9)
Behavior3/5

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

The description outlines the cycle stages and early stopping behavior, but lacks disclosure about side effects, state mutations, or required permissions, which is important given no annotations.

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?

The description is a single, well-structured sentence listing the pipeline, followed by a concise explanation of early stopping. No unnecessary words.

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

Completeness3/5

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

Given the complexity (17 params, no output schema, no annotations), the description provides core functionality but lacks details on return values, error conditions, and complete parameter semantics.

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

Parameters3/5

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

With 82% schema coverage, the description adds marginal value by referencing stopWhenSatisfied and some thresholds, but does not explain all 17 parameters in depth.

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: 'Run one or more ACM cycles' and lists the pipeline stages, distinguishing it from sibling tools that focus on specific aspects like active inference or convergence.

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

Usage Guidelines4/5

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

The description implies usage for running multiple cycles with early stopping via stopWhenSatisfied, but does not explicitly contrast with other tcai tools or specify when not to use it.

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/christophejlegros-lgtm/ASTRA-Unified-ResearchLab-MCP-v2.9'

If you have feedback or need assistance with the MCP directory API, please join our Discord server