Skip to main content
Glama
christophejlegros-lgtm

ASTRA — Unified Research Lab + MCP Server

tcai_reset

Reset the TCAI consciousness system to its initial state, clearing workspace, memory, emotion, and metrics.

Instructions

Reset the TCAI consciousness system (workspace, memory, emotion, metrics)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations provided, the description bears the full burden of disclosing behavior. It states that the tool resets multiple subsystems but does not indicate if the action is destructive, irreversible, or requires special permissions. For a reset operation, this omission is significant.

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 sentence, front-loaded with the verb 'Reset', and efficiently communicates the tool's purpose without extraneous words.

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?

Given the complexity of resetting a consciousness system with multiple components, the description is too brief. It lacks warnings about data loss, side effects, or usage context. An output schema is absent, so the description should provide more behavioral detail.

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?

The tool has zero parameters, so the schema is trivially covered. The description adds no parameter-specific meaning, but since no parameters exist, the baseline of 4 is appropriate. The description does not need to elaborate on inputs.

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 resets the TCAI consciousness system, specifying four components (workspace, memory, emotion, metrics). The verb 'Reset' is specific, and the resource is well-defined, distinguishing it from siblings like 'snn_reset' (which resets a different subsystem) and 'tcai_workspace_state' (which reads state).

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'snn_reset' or 'tcai_cycle'. There is no mention of prerequisites, consequences, or context for invocation. The description is purely a statement of action.

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.8'

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