Skip to main content
Glama
christophejlegros-lgtm

ASTRA — Unified Research Lab + MCP Server

tcai_cycle

Run recursive cycles of consciousness simulation (SNN to qualia to self-model) with early stopping when the loop reaches a stable, satisfied state.

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
Behavior4/5

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

Given no annotations, the description discloses the pipeline steps and the early halt behavior. While it doesn't cover side effects or authorization, it provides significant context for a complex tool.

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 a single, information-dense sentence that front-loads the pipeline. It is efficient but could be split for readability.

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?

With 15 parameters, no output schema, and no annotations, the description provides a high-level process but lacks details on return values, interpretation of results, and handling of edge cases.

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 high (80%), so many parameters have descriptions. The description adds value by explaining the overall process and the stopWhenSatisfied mechanism, but doesn't detail individual parameters beyond the schema.

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 explicitly states it runs ACM cycles and lists the entire pipeline (SNN signals through second-order loop), making the tool's purpose clear. It also distinguishes from sibling tools by focusing on cycle execution.

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 for running cycles and mentions stopWhenSatisfied for early halting, but does not provide explicit guidance on when to use this tool versus alternatives, nor does it state prerequisites or 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.6'

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