Skip to main content
Glama
Sign In
RLM MCP Server

RLM MCP Server

by win10ogod
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Clear Session

rlm_clear_session
DestructiveIdempotent

Clears all contexts, variables, and history from a session, resetting it to an empty state for fresh usage.

Instructions

Clear all data from a session (contexts, variables, history).

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

Input Schema

NameRequiredDescriptionDefault
session_idNoSession ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already indicate destructive and idempotent behavior. Description adds concrete context about which data types are affected (contexts, variables, history), going beyond the annotation flags without contradicting them.

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?

Single concise sentence, front-loaded with the clear verb, efficiently conveys the tool's scope. No unnecessary words.

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 param and annotations covering safety profile, the description sufficiently states what is cleared. Could benefit from a caution phrase, but given low complexity and sibling context, it is adequately complete.

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 fully documents the single session_id parameter with a basic description. Tool description adds no extra meaning about the parameter's format or necessity beyond what the schema provides, so baseline 3 is appropriate.

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?

Description uses specific verb 'Clear' with resource 'session' and details what is cleared (contexts, variables, history). Clearly distinguishes from sibling tools like get_session_info or create_session.

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 explicit when-to-use or alternative guidance. Does not mention that this is destructive or irreversible, nor when a user should prefer clearing versus creating a new session.

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