Skip to main content
Glama
Sign In
ASTRA Unified Research Lab MCP Server

ASTRA Unified Research Lab MCP Server

by christophejlegros-lgtm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

tcai_reset

Resets the TCAI consciousness system, clearing workspace, memory, emotion, and metrics to restore a clean state for simulation experiments.

Instructions

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tcai_reset"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A3.5/5.0
Behavior2/5

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

The description lists the affected components but does not disclose that a reset is likely destructive, irreversible, or has side effects. Since no annotations are provided, the description carries the full burden and this is a significant transparency gap.

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, concise sentence that front-loads the action and resource. It avoids redundancy and is appropriately sized for a tool with no parameters.

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?

While the description covers the basic function and scope, it lacks details about the consequences of a reset, such as whether it clears all data, requires confirmation, or affects other systems. For a mutation tool with no annotations, this leaves the agent without a complete understanding.

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 and the schema coverage is 100%, so there is nothing for the description to add param-wise. The baseline for 0 params is 4, and the description does not omit any necessary parameter information.

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 action 'Reset' and the resource 'TCAI consciousness system', listing the specific components (workspace, memory, emotion, metrics). This distinguishes it from sibling tools like tcai_cycle or tcai_workspace_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?

The description provides no guidance on when to use this tool versus alternatives, no prerequisites, or exclusions. It only states what the tool does, not when it should be called.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools