SageMath MCP Server

reset_sage_session

DestructiveIdempotent

Clear all variables and state in a SageMath workspace to start fresh. Use when the current session needs isolation or recovery.

Instructions

Reset the SageMath session state for the current MCP session

Input Schema

TableJSON Schema

Name	Required	Description	Default
`session`	No	Workspace to use, as a name or a portable handle. Workspaces have independent variables. A name is scoped to this MCP session; a handle returned by start_sage_session (workspace_token) reaches the same workspace across reconnects and is a bearer credential -- keep it secret. Omit for 'default'.	default

Output Schema

TableJSON Schema

Name	Required	Description	Default
`message`	No		Session cleared

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.7.0Sep 12, 2026

changedInput schema / properties / session / description

Previous value: -"Named workspace to use. Workspaces have independent variables; omit for 'default'."New value: +"Workspace to use, as a name or a portable handle. Workspaces have independent variables. A name is scoped to this MCP session; a handle returned by start_sage_session (workspace_token) reaches the same workspace across reconnects and is a bearer credential -- keep it secret. Omit for 'default'."

Changed1 schema field changedv0.5.0Aug 14, 2026

addedInput schema / properties / session

Added value: +{
+  "default": "default",
+  "description": "Named workspace to use. Workspaces have independent variables; omit for 'default'.",
+  "type": "string"
+}

First observedv0.3.1Jul 31, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds only the notion of clearing session state and does not say what specifically is destroyed (variables, definitions, workspace contents) or whether the session remains usable afterward.

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 efficient sentence with the key concept front-loaded. It is tight but arguably too terse given the ambiguity against sibling session tools, so not a 5.

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?

With an output schema present, return values need no explanation, and the parameter semantics are fully covered by the schema. However, for a destructive operation sitting in a family of session tools, the description omits what reset preserves versus destroys and how it differs from stop/cancel.

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%, and the schema's parameter description is unusually rich (name vs. portable handle, bearer-credential warning, default behavior). The tool description adds nothing beyond this, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Reset the SageMath session state"), which is clearer than a tautology, but it does not differentiate from closely related siblings such as stop_sage_session, cancel_sage_session, or start_sage_session. An agent cannot tell from the text whether "reset" clears variables, restarts the kernel, or recreates the workspace.

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 when-to-use guidance, prerequisites, or alternative tools are named, despite a crowded family of session-lifecycle siblings (start/stop/cancel/interrupt/list). The agent is left to infer that reset is the state-clearing operation rather than a teardown.

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