Skip to main content
Glama
Sign In
openclaw-control-mcp

openclaw-control-mcp

by smurfy92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

openclaw_doctor_memory_resetGroundedShortTerm

Clears the grounded short-term memory store, removing an agent's recent recall. Use to reset context, but note this action is destructive.

Instructions

Wipe the grounded short-term memory store. Wraps doctor.memory.resetGroundedShortTerm. DESTRUCTIVE — agents lose their recent recall.

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": "openclaw_doctor_memory_resetGroundedShortTerm"
  }
}

Input Schema

NameRequiredDescriptionDefault
instanceNoOptional OpenClaw instance to route this call to (e.g. 'default', 'work'). Falls back to the active default instance, or the OPENCLAW_GATEWAY_URL/TOKEN env vars when set. List configured instances with openclaw_setup_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A4/5.0
Behavior4/5

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

Without annotations, the description effectively discloses the destructive nature of the tool. It mentions that agents lose recent recall, providing sufficient behavioral context.

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?

Two sentences, front-loaded with action and a clear warning. Every word is purposeful with no redundancy.

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?

For a simple destructive tool with one optional parameter, the description provides adequate context. It could mention if repeated calls cause issues, but not necessary.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the description does not add additional meaning to the single parameter beyond what the schema already provides.

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 'Wipe the grounded short-term memory store' with a specific verb and resource, and it distinguishes itself from other memory-related siblings like resetDreamDiary.

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 warns 'DESTRUCTIVE — agents lose their recent recall' but does not provide explicit guidance on when to use or alternatives. It implies caution but lacks full usage context.

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