Skip to main content
Glama
Sign In
ASTRA

ASTRA

by christophejlegros-lgtm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

tcai_reset

DestructiveIdempotent

Resets the TCAI consciousness system's workspace, memory, emotion, and metrics to clear accumulated state and restore default settings.

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.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds value by enumerating what gets reset (workspace, memory, emotion, metrics), which tells the agent the blast radius. It still doesn't say whether data is recoverable or whether a confirmation step is expected.

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?

A single front-loaded sentence with no filler. The verb and scope come first, and the parenthetical list of affected subsystems is efficient rather than padded.

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

Completeness4/5

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

With no parameters, no output schema, and annotations that already carry the destructive/idempotent profile, the description only needs to convey what the operation affects, which it does. The main residual gap is the absence of any recovery or confirmation context for a destructive reset.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. No parameter semantics are needed or missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Reset) and resource (TCAI consciousness system) and scopes it by naming the affected components (workspace, memory, emotion, metrics). This distinguishes it from the similarly named sibling snn_reset, which targets 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 gives no when-to-use guidance, no prerequisites, and no alternatives. An agent must infer that this is for wiping TCAI state, and only the annotations (not the description) hint at how consequential that is.

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