Skip to main content
Glama
christophejlegros-lgtm

ASTRA Unified Research Lab MCP Server

tcai_reset

Reset the TCAI consciousness system, clearing workspace, memory, emotion, and metrics to restore a clean state for new simulations.

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, the description carries the full burden of behavioral disclosure. It names the components being reset but does not explicitly state that the reset is destructive, irreversible, or that it clears all current state. The word 'reset' implies wiping, but critical consequences like data loss and system disruption are left unstated.

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, front-loaded sentence that efficiently conveys the action and scope. Every word is purposeful with no filler, making it highly concise and well-structured.

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?

While the tool is simple with no parameters and no output schema, a reset operation is destructive and context-dependent. The description omits crucial information such as the irreversible nature, potential impact on running processes, and any warnings. It gives only the basic scope without the broader context an agent needs.

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 there is no parameter semantics to elaborate. A baseline score of 4 is appropriate since the description need not compensate for any schema gaps.

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 specific action 'Reset' and the resource 'TCAI consciousness system', with the scope explicitly listing workspace, memory, emotion, and metrics. This distinguishes it from sibling tools like snn_reset, which reset a different subsystem.

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?

The description provides no guidance on when to use this tool versus alternatives, no exclusions, and no context on prerequisites or scenarios where resetting is appropriate. It merely states what it does, leaving the agent without usage direction.

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

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