Skip to main content
Glama
Sign In
Janus MCP

Janus MCP

by DeanWard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

remove_session

Delete a session by ID to free up memory. Use when a session ends or is no longer needed to release resources.

Instructions

Remove a session and free up memory

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": {
      "sessionId": "<sessionId>"
    },
    "name": "remove_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYesThe session ID to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It says 'remove' but not whether the removal is irreversible, whether an active session is terminated cleanly, what happens to the associated memory or resources, or what error occurs for an invalid sessionId. For a destructive operation with zero annotation coverage, this is thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted words. It is efficient, though so brief that it leaves obvious behavioral questions unanswered rather than being merely restrained.

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?

The tool is simple (one required parameter, no output schema needed for a removal), so the description is minimally sufficient to call it. However, with no annotations and a destructive action, an agent still lacks confirmation of irreversibility and failure modes.

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 description coverage is 100% with a single well-documented sessionId, so the baseline is 3. The description adds no formatting, origin, or validity detail for the parameter beyond what the schema already states.

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 (Remove) and resource (session), and the side effect ('free up memory') clarifies intent. It contrasts implicitly with the sibling initialize_session, but never names it or any other sibling, so sibling differentiation is left to inference.

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 on when to call this, no prerequisites (must the session exist?), no exclusions, and no mention of when to prefer an alternative such as letting a session expire. 'Free up memory' hints at a motivation but is not actionable usage guidance.

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