Skip to main content
Glama

Stat Reset Session

stat_reset_session

Clear all datasets, results, and figures to start a fresh session and prevent stale objects from affecting a new, separate analysis.

Instructions

Clear all datasets, results and figures, starting a fresh session.

WHEN TO USE: before starting a genuinely separate analysis, to avoid reading stale objects. WHEN NOT TO USE: casually — loaded data are lost.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations exist, so the description carries the burden, and it delivers the critical detail: all datasets, results and figures are destroyed and loaded data are lost. It does not explicitly state irreversibility or whether a confirmation step is required, leaving a small gap for a destructive operation.

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?

Three tight segments: the action, the positive trigger, the negative trigger. Every sentence earns its place, and the destructive scope is front-loaded before the usage guidance.

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 zero-parameter destructive reset, the essential facts (what is cleared, when to invoke) are present, and an output schema exists so return values need not be explained. Only an explicit note on irreversibility or required confirmation would fully close the loop.

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 takes zero parameters, so there is no parameter meaning to add; the schema is fully closed with additionalProperties false. Nothing in the description is needed or missing on this dimension.

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 and resource set: clears datasets, results and figures to start a fresh session. An agent can distinguish it from read-only siblings like stat_session_info or stat_describe_data. It stops short of naming a sibling it might be confused with, so not a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit WHEN TO USE ('before a genuinely separate analysis, to avoid reading stale objects') and WHEN NOT TO USE ('casually — loaded data are lost'). The condition that selects this tool versus avoiding it is unambiguous, with no reliance on inference.

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