rnaseq-mcp

Overview Schema Source Related Servers Discussions Admin

reset_session

Destroy the current Docker container and start a fresh one with the same anonymized data, clearing all in-memory state and output files.

Instructions

Destroy the current Docker container and start a fresh one with the same anonymized data. Use this to clear all in-memory R/Python state and /output files.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description fully discloses the destructive nature ('Destroy the current Docker container') and the effects ('clear all in-memory R/Python state and /output files'). It lacks details on whether the action is irreversible or if other sessions are affected, but overall provides good 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 concise sentences with no fluff. The first states the action, the second provides usage context. Every sentence earns its place.

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?

The description covers the core functionality and gives a clear usage context. It mentions that anonymized data is retained and that output files are cleared. However, it does not mention if there is any confirmation step or undo capability, which might be relevant for a destructive action. Overall, sufficiently complete for a simple tool.

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 has zero parameters, so the schema coverage is 100%. The description does not need to add parameter information. Baseline for zero-parameter tools is 4, and the description meets that without needing to elaborate on parameters.

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 'Destroy the current Docker container and start a fresh one with the same anonymized data.' It uses a specific verb (destroy, start) and names the resource (Docker container). It also distinguishes from sibling tools like execute_python and execute_r, which run code rather than resetting the environment.

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 says 'Use this to clear all in-memory R/Python state and /output files,' which implies when to use. However, it provides no guidance on when not to use, no mention of prerequisites or consequences, and no alternatives listed. This is implied usage without explicit exclusions.

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

Deploy Server