Skip to main content
Glama
pzfreo

build123d-mcp

reset

Clear the current session to an empty state, removing all snapshots. Use this to start fresh without exiting.

Instructions

Clear the current session back to empty state, including all snapshots.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • MCP tool registration for 'reset' — decorates the handler function with @mcp.tool() making it available via MCP protocol.
    @mcp.tool()
    def reset() -> str:
        """Clear the current session back to empty state, including all snapshots."""
        return _session.reset()
  • Session.reset() — core implementation that clears the namespace, current shape, registered objects, snapshots, and last error, then re-injects restricted builtins.
    def reset(self) -> None:
        self.namespace.clear()
        self.current_shape = None
        self.objects.clear()
        self.snapshots.clear()
        self.last_error_detail = None
        self._inject_builtins()
  • Worker dispatch handler for the 'reset' operation — calls session.reset() when the worker receives a reset request.
    if op == "reset":
        session.reset()
        return "Session reset."
Behavior4/5

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

With no annotations, the description clearly states the tool clears the session and snapshots, which is transparent about its effect. However, it does not mention irreversibility or any side effects, which slightly reduces completeness.

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?

A single sentence that is clear and front-loaded with the action and scope. Every word is essential, and there is no extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with no parameters, and an output schema is present. The description fully captures the tool's behavior and scope, making it complete for agent invocation.

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 input schema has zero parameters, so no parameter documentation is needed. The description adds no parameter info, but baseline is 4 due to full schema coverage (100%).

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 explicitly states the tool resets the session to an empty state, including snapshots, which distinguishes it from siblings like save_snapshot and restore_snapshot. The verb 'clear' and resource 'current session' are specific and unambiguous.

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 is provided on when to use this tool versus alternatives (e.g., save_snapshot, restore_snapshot). The description implies usage for resetting state but does not explicitly state prerequisites or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pzfreo/build123d-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server