GoClaw MCP Server

goclaw_session_reset

Clear chat message history to reset a session in the GoClaw AI gateway infrastructure.

Instructions

Reset a chat session (clear message history)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_key": "<session_key>"
    },
    "name": "goclaw_session_reset"
  }
}

Input Schema

Name	Required	Description	Default
`session_key`	Yes	Session key to reset

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 15, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool resets a session by clearing message history, but doesn't mention whether this action is reversible, requires specific permissions, affects other session data, or has side effects like rate limits. This leaves significant gaps for a mutation tool.

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, efficient sentence that front-loads the purpose ('Reset a chat session') and adds clarifying detail ('clear message history') without any wasted words. It's appropriately sized for a simple tool.

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?

For a mutation tool with no annotations and no output schema, the description is minimal but covers the basic action. It lacks details on behavioral traits, usage context, and output expectations, making it adequate but with clear gaps given the tool's potential complexity.

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?

The input schema has 100% description coverage, with 'session_key' clearly documented. The description doesn't add any parameter details beyond what the schema provides, such as format examples or constraints. Baseline 3 is appropriate since the schema does the heavy lifting.

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?

The description clearly states the action ('Reset a chat session') and the effect ('clear message history'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'goclaw_session_delete' or 'goclaw_session_label', which might have overlapping or related purposes in session management.

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 such as 'goclaw_session_delete' (which might permanently remove a session) or 'goclaw_session_label' (which might modify session metadata). The description lacks context on prerequisites, timing, or exclusions for usage.

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

Deploy Server