Skip to main content
Glama

status

Check the undo system's current state: view checkpoint count, stack size, and whether undo operations are available.

Instructions

Get current status of the undo system (checkpoint count, number of checkpoints in the stack, and whether undo is possible)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:69-76 (registration)
    Registers the 'status' tool with its name, description, and input schema (no parameters required).
    {
      name: "status",
      description: "Get current status of the undo system (checkpoint count, number of checkpoints in the stack, and whether undo is possible)",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • The main handler for the 'status' tool in the CallToolRequestSchema switch statement. It calls changeTracker.getStatus() and formats a text response with checkpoint count and undo availability.
    case "status": {
      const status = changeTracker.getStatus();
      return {
        content: [
          {
            type: "text",
            text: `📊 Undo System Status:\nCheckpoints: ${status.checkpointCount}\nCan Undo: ${status.canUndo}`,
          },
        ],
      };
    }
  • Core implementation of status logic in ChangeTracker class. Deduplicates checkpoints and returns the count and whether undo is possible.
    getStatus(): {
      checkpointCount: number;
      canUndo: boolean;
    } {
      // Deduplicate checkpoints before returning status
      this.deduplicateCheckpoints();
      
      return {
        checkpointCount: this.undoStack.length,
        canUndo: this.undoStack.length > 0,
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It describes the return data but doesn't disclose behavioral traits like whether this is a read-only operation, if it has side effects, performance characteristics, or error conditions. The description is purely informational about output.

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?

The description is a single, well-structured sentence that efficiently conveys the tool's purpose and output details without any redundant or unnecessary information. It's appropriately sized and front-loaded.

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?

Given the tool has no parameters, no annotations, and no output schema, the description adequately explains what the tool does and what information it returns. However, it lacks details on behavioral aspects like side effects or error handling, which would be beneficial for a tool interacting with system state.

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 0 parameters, and schema description coverage is 100% (empty schema). The description appropriately doesn't add parameter details beyond what the schema provides, which is minimal since there are no parameters. Baseline for 0 parameters is 4.

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 the specific action ('Get current status') and the exact resource ('undo system'), listing the specific data points returned (checkpoint count, number of checkpoints in stack, undo possibility). It distinguishes from siblings like 'checkpoint' (create), 'cleanup' (remove), 'list_undos' (list), and 'undo' (execute).

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 implies usage context by specifying what information is retrieved about the undo system, suggesting it's for monitoring state. However, it doesn't explicitly state when to use this tool versus alternatives like 'list_undos' or provide any exclusion criteria or prerequisites.

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/khalilbalaree/undo-mcp'

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